---
compositor/screenshooter.c |6 ++
1 files changed, 2 insertions(+), 4 deletions(-)
diff --git a/compositor/screenshooter.c b/compositor/screenshooter.c
index c0757db..53ed931 100644
--- a/compositor/screenshooter.c
+++ b/compositor/screenshooter.c
@@ -34,7 +34,7 @@ screenshooter_shoot
---
clients/view.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/clients/view.c b/clients/view.c
index 8f83b9c..05edf3f 100644
--- a/clients/view.c
+++ b/clients/view.c
@@ -101,6 +101,7 @@ view_draw(struct view *view)
cairo_fill(cr);
poppler_page_render(p
---
clients/view.c | 18 +-
1 files changed, 13 insertions(+), 5 deletions(-)
diff --git a/clients/view.c b/clients/view.c
index d083034..8f83b9c 100644
--- a/clients/view.c
+++ b/clients/view.c
@@ -64,8 +64,6 @@ view_draw(struct view *view)
window_get_child_allocation
---
clients/view.c | 22 +-
1 files changed, 17 insertions(+), 5 deletions(-)
diff --git a/clients/view.c b/clients/view.c
index 1e0cbb0..d083034 100644
--- a/clients/view.c
+++ b/clients/view.c
@@ -193,6 +193,7 @@ view_create(struct display *display, uint32_t key, const
ch
---
clients/view.c | 68 ++--
1 files changed, 51 insertions(+), 17 deletions(-)
diff --git a/clients/view.c b/clients/view.c
index cc3206d..1e0cbb0 100644
--- a/clients/view.c
+++ b/clients/view.c
@@ -107,38 +107,72 @@ redraw_handler(struct w
---
clients/view.c | 13 +
1 files changed, 1 insertions(+), 12 deletions(-)
diff --git a/clients/view.c b/clients/view.c
index 9e19a5a..cc3206d 100644
--- a/clients/view.c
+++ b/clients/view.c
@@ -45,13 +45,10 @@
struct view {
struct window *window;
struct display
---
clients/view.c | 10 --
1 files changed, 8 insertions(+), 2 deletions(-)
diff --git a/clients/view.c b/clients/view.c
index 88c59ad..9e19a5a 100644
--- a/clients/view.c
+++ b/clients/view.c
@@ -127,14 +127,20 @@ key_handler(struct window *window, struct input *input,
uint32_t time,
On Tue, Jan 25, 2011 at 4:02 PM, Zan Dobersek wrote:
> Thanks for the reply.
> The following is what pushed me into researching the problem - I've created
> a test application that sets up a display and tries to create a client that
> connects to that display, but the client does not connect.
> Ju
Thanks for the reply.
The following is what pushed me into researching the problem - I've created
a test application that sets up a display and tries to create a client that
connects to that display, but the client does not connect.
Just as in compositor, I create a wl_display, add a socket to it
Because gdk_pixbuf_unref is deprecated and for compatability with
gdk-pixbuf 2.21.4.
---
clients/window.c |8
compositor/compositor.c|4 ++--
compositor/screenshooter.c |4 ++--
3 files changed, 8 insertions(+), 8 deletions(-)
diff --git a/clients/window.c b/cli
(this is going off topic.. oh well)
On 01/25/2011 12:31 AM, ext Kristian Høgsberg wrote:
The "input_device" interface describes the entire input protocol as it
is now. Obviously, there's work to do, right now it's sort of like
core input + mpx. But the point is, we can phase this out in favour
As Ben just alluded to in another thread, yesterday Kristian committed
Ben's fix for this problem to mesa git. So to run Wayland on non-Intel
video cards, you need Mesa from git at least as new as yesterday.
The commits:
http://cgit.freedesktop.org/mesa/mesa/commit/?id=f1452844fe2522387bbc6633f2
2011/1/25 Chase Douglas :
> On 01/24/2011 09:18 PM, Kristian Høgsberg wrote:
>> I expect gesture recognition will work much the same way. The
>> compositor gets the input events before anybody else and can decide
>> whether it's a global gesture and keep the events to itself or to
>> forward them
On 01/24/2011 09:18 PM, Kristian Høgsberg wrote:
> I expect gesture recognition will work much the same way. The
> compositor gets the input events before anybody else and can decide
> whether it's a global gesture and keep the events to itself or to
> forward them to the application. There is no
Hi,
this is not meant as an "official build guide", it's rather "what configuration is
working for me":
$ lspci | grep VGA
01:00.0 VGA compatible controller: ATI Technologies Inc Radeon HD 3870
$ uname -r
2.6.37-trunk-amd64
$ cat /etc/apt/sources.list
deb http://ftp.de.debian.org/debian/ test
You need a newer mesa version (from git) for the
GL_EXT_texture_format_BGRA error.
The DRM mode didnt work well for me with the r600 pageflipping
patches.. Maybe you have more luck.
But wayland does work good with r600 using the x11-compositor.
-Ben
2011/1/25 :
> Hi,
>
> I am trying to run
Hi,
I am trying to run Wayland on an Arch Linux system with kernel 2.6.38 and Mesa
git. The system has an AMD R600 card, which, according to the Wayland FAQ,
doesn't work yet due to the driver not supporting page flipping, but as that
changed for kernel 2.6.38 [1], I figured that it might work
On Tue, Jan 25, 2011 at 6:01 AM, Tim Wiederhake wrote:
> fixes segfault when active tty could not be opened
> fixes copy-paste mistake.
Thanks, applied. A little nitpick about the commit message
formatting: could you capitalize the title and format the body as
regular text (regular punctuation a
fixes segfault when active tty could not be opened
fixes copy-paste mistake.
---
compositor/tty.c |8
1 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/compositor/tty.c b/compositor/tty.c
index 70c319d..6314b14 100644
--- a/compositor/tty.c
+++ b/compositor/tty.c
@@ -148,
2011/1/25 Bill Spitzak :
> I'm wary of a "config" file the window manager reads. What users want to do
> is go into the application and run some control panel that says "now the
> shortcut X+Y+Z does this" and it starts happening, and they can then change
> their mind and it goes back to the way it
20 matches
Mail list logo
