On Wed, 2012-07-25 at 09:33 -0400, Kristian Høgsberg wrote:
> On Wed, Jul 25, 2012 at 1:00 AM, Bill Spitzak wrote:
> > On 07/24/2012 06:10 PM, Juan Zhao wrote:
> >
> >> Is it in the condition that, click any area of the window could drag and
> >> move the window? Some user case is, only the title
Oddly enough it was working on my old 10.04 system. You would think
things would get better, not worse.
I am under the impression that if I do this, I can go back to the nvidia
driver as well?
Philipp Brüschweiler wrote:
I'm on nouveau as well. The drm backend has never worked for me.
On We
Kristian Høgsberg wrote:
We added wl_shell_surface, because we had a lot
of requests on wl_shell that went like: wl_shell.set_fullscreen(shell,
surface), ie, took the shell and a surface, and in effect were surface
requests. So the wl_shell_surface is almost just protocol syntatic
sugar, and I'
Juan Zhao wrote:
On Tue, 2012-07-24 at 23:17 -0700, Bill Spitzak wrote:
On 07/24/2012 10:32 PM, Juan Zhao wrote:
Therefore I suggest that the sample client work as proposed, and
only
prevent that point from being obscured.
Do you mean, avoiding the places where it could triger the drag to
Kristian Høgsberg wrote:
I had the same feeling here. And we should change wl_shell to
wl_desktop_shell for once.
Wouldn't that mean clients need to know what kind of shell they are
talking to? I would make wl_shell be the common api and all types of
shells are expected to implement it as we
On Wed, Jul 25, 2012 at 07:10:33PM +0200, Andre Heider wrote:
Looks good, thanks.
Kristian
> ---
> clients/window.c | 13 -
> 1 file changed, 13 deletions(-)
>
> diff --git a/clients/window.c b/clients/window.c
> index 186eed9..c55ec77 100644
> --- a/clients/window.c
> +++ b/clie
On Wed, Jul 25, 2012 at 02:33:42PM +0200, Olivier Blin wrote:
Applied this one, thanks.
Kristian
> ---
> clients/gears.c | 11 +++
> 1 file changed, 11 insertions(+)
>
> diff --git a/clients/gears.c b/clients/gears.c
> index 166e6a4..70ec86c 100644
> --- a/clients/gears.c
> +++ b/client
On Wed, Jul 25, 2012 at 1:41 PM, Pekka Paalanen wrote:
> On Wed, 25 Jul 2012 18:20:34 +0200
> Olivier BLIN wrote:
>
>> On 07/25/2012 05:00 PM, Pekka Paalanen wrote:
>> > Gears will now need the same disclaimer as glxgears has, otherwise end
>> > users will start using this as a generic Wayland pe
On Wed, 25 Jul 2012 18:20:34 +0200
Olivier BLIN wrote:
> On 07/25/2012 05:00 PM, Pekka Paalanen wrote:
> > Gears will now need the same disclaimer as glxgears has, otherwise end
> > users will start using this as a generic Wayland performance
> > benchmark. I can imagine some headlines on Phoro
---
clients/window.c | 13 -
1 file changed, 13 deletions(-)
diff --git a/clients/window.c b/clients/window.c
index 186eed9..c55ec77 100644
--- a/clients/window.c
+++ b/clients/window.c
@@ -323,16 +323,6 @@ enum window_location {
WINDOW_CLIENT_AREA = 18,
};
-const char *o
On 07/25/2012 05:00 PM, Pekka Paalanen wrote:
Gears will now need the same disclaimer as glxgears has, otherwise end
users will start using this as a generic Wayland performance
benchmark. I can imagine some headlines on Phoronix when they compare
Wayland gears with glxgears and draw wildly inc
On Wed, 25 Jul 2012 15:19:23 +0200
Olivier Blin wrote:
> ---
> clients/gears.c | 29 +
> 1 file changed, 29 insertions(+)
>
> diff --git a/clients/gears.c b/clients/gears.c
> index 70ec86c..19165e7 100644
> --- a/clients/gears.c
> +++ b/clients/gears.c
> @@ -59,6 +59
On Wed, Jul 25, 2012 at 02:51:09PM +0100, Damien Lespiau wrote:
> From: Damien Lespiau
>
> setbacklight depends on udev and drm, one cannot just add the -l flags
> if you want to support unusual install paths.
Thanks Damien, applied and pushed.
Kristian
> ---
> configure.ac |1 +
> t
On Wed, Jul 25, 2012 at 9:11 AM, Daniel Stone wrote:
> Hi Ander,
>
> On 25 July 2012 12:57, Ander Conselvan de Oliveira
> wrote:
>> On 07/23/2012 09:55 PM, Daniel Stone wrote:
>>> @@ -1394,8 +1414,13 @@ surface_attach(struct wl_client *client,
>>>
>>> weston_surface_attach(&es->surface,
From: Damien Lespiau
setbacklight depends on udev and drm, one cannot just add the -l flags
if you want to support unusual install paths.
---
configure.ac |1 +
tests/Makefile.am |3 ++-
2 files changed, 3 insertions(+), 1 deletions(-)
diff --git a/configure.ac b/configure.ac
index
On Wed, Jul 25, 2012 at 6:45 AM, Ander Conselvan de Oliveira
wrote:
> On 07/23/2012 09:54 PM, Daniel Stone wrote:
>>
>> The wl_cursor object represents a visible on-screen cursor, with
>> co-ordinates and a surface image. Add hooks for compositors to be able
>> to discover new cursors and be info
On Wed, Jul 25, 2012 at 1:00 AM, Bill Spitzak wrote:
> On 07/24/2012 06:10 PM, Juan Zhao wrote:
>
>> Is it in the condition that, click any area of the window could drag and
>> move the window? Some user case is, only the title bar area could be
>> dragged and moved.
>
>
> My understanding is that
On Wed, Jul 25, 2012 at 3:35 AM, Tiago Vignatti
wrote:
> On 07/24/2012 11:48 PM, Pekka Paalanen wrote:
>>
>> On Tue, 24 Jul 2012 16:32:18 -0400
>> Kristian Høgsberg wrote:
>>
>>> With the 0.95 release we start maintaining protocol and client API
>>> stability. Going forward, we will try to not b
---
clients/gears.c | 29 +
1 file changed, 29 insertions(+)
diff --git a/clients/gears.c b/clients/gears.c
index 70ec86c..19165e7 100644
--- a/clients/gears.c
+++ b/clients/gears.c
@@ -59,6 +59,8 @@ struct gears {
GLint gear_list[3];
int fullscreen;
Hi Rob,
On 24 July 2012 13:01, Rob Bradford wrote:
> On 23 July 2012 19:55, Daniel Stone wrote:
>> - wl_pointer_set_cursor(input->pointer, input->display->serial,
>> - input->pointer_surface,
>> - image->hotspot_x, image->hotspot_y);
Hi Ander,
On 25 July 2012 12:57, Ander Conselvan de Oliveira wrote:
> On 07/23/2012 09:55 PM, Daniel Stone wrote:
>> @@ -1394,8 +1414,13 @@ surface_attach(struct wl_client *client,
>>
>> weston_surface_attach(&es->surface, buffer);
>>
>> - if (buffer && es->configure)
>> + if
On 07/25/2012 03:33 PM, Olivier Blin wrote:
---
clients/gears.c | 31 +++
1 file changed, 31 insertions(+)
diff --git a/clients/gears.c b/clients/gears.c
index 70ec86c..8e7d4df 100644
--- a/clients/gears.c
+++ b/clients/gears.c
@@ -59,6 +59,8 @@ struct gears {
---
clients/gears.c | 11 +++
1 file changed, 11 insertions(+)
diff --git a/clients/gears.c b/clients/gears.c
index 166e6a4..70ec86c 100644
--- a/clients/gears.c
+++ b/clients/gears.c
@@ -58,6 +58,7 @@ struct gears {
int last_x, last_y;
GLint gear_list[3];
+ int fu
---
clients/gears.c | 31 +++
1 file changed, 31 insertions(+)
diff --git a/clients/gears.c b/clients/gears.c
index 70ec86c..8e7d4df 100644
--- a/clients/gears.c
+++ b/clients/gears.c
@@ -59,6 +59,8 @@ struct gears {
GLint gear_list[3];
int fullscreen
Hi Daniel,
On 07/23/2012 09:55 PM, Daniel Stone wrote:
Port the existing manual (and somewhat fragile) cursor-handling code to
the new wl_cursor interface.
Signed-off-by: Daniel Stone
---
clients/window.c |6 +-
src/compositor.c | 378 ---
On 07/23/2012 09:54 PM, Daniel Stone wrote:
The wl_cursor object represents a visible on-screen cursor, with
co-ordinates and a surface image. Add hooks for compositors to be able
to discover new cursors and be informed when they change, and have the
core implementation track the location.
I l
On Tue, 2012-07-24 at 23:17 -0700, Bill Spitzak wrote:
> On 07/24/2012 10:32 PM, Juan Zhao wrote:
>
> >> Therefore I suggest that the sample client work as proposed, and
> only
> >> prevent that point from being obscured.
> >
> > Do you mean, avoiding the places where it could triger the drag to
>
I'm on nouveau as well. The drm backend has never worked for me.
On Wed, Jul 25, 2012 at 9:51 AM, Scott Moreau wrote:
> On Wed, Jul 25, 2012 at 1:39 AM, Philipp Brüschweiler
> wrote:
>>
>> I had the same problem. Enabling gallium-egl fixed it:
>>
>> On the mesa autogen.sh line (line 322) replace
On Wed, Jul 25, 2012 at 1:39 AM, Philipp Brüschweiler wrote:
> I had the same problem. Enabling gallium-egl fixed it:
>
> On the mesa autogen.sh line (line 322) replace '--disable-gallium-egl'
> by '--enable-gallium-egl'
>
> Cheers,
> Philipp
>
>
Using which driver? Does drm backend work?
Scott
>
> xwayland failed to build:
>
> checking for SHA1 implementation... configure: error: No suitable SHA1
> implementation found
>
> I disabled xwayland, though I am interested in it.
>
You might need to install openssl development package for your distro.
>
> I then tried to run wayland and (aft
On 07/25/2012 09:25 AM, Bill Spitzak wrote:
xwayland failed to build:
checking for SHA1 implementation... configure: error: No suitable SHA1
implementation found
I'm using gcrypt in my system ('sudo apt-get install libgcrypt11-dev').
But X does let you choose among a bunch of SHA1 libraries.
I had the same problem. Enabling gallium-egl fixed it:
On the mesa autogen.sh line (line 322) replace '--disable-gallium-egl'
by '--enable-gallium-egl'
Cheers,
Philipp
On Wed, Jul 25, 2012 at 8:25 AM, Bill Spitzak wrote:
> On 07/24/2012 09:46 PM, Bill Spitzak wrote:
>
>>> You took the script th
On 07/24/2012 11:48 PM, Pekka Paalanen wrote:
On Tue, 24 Jul 2012 16:32:18 -0400
Kristian Høgsberg wrote:
With the 0.95 release we start maintaining protocol and client API
stability. Going forward, we will try to not break any clients or
toolkits that are written agains the 0.95 protocol and
On 07/24/2012 09:46 PM, Bill Spitzak wrote:
You took the script that checks out the 0.85 version of wayland and
weston,
which is 5 months old. Before, you were using master.
doh! Thank you! The web page was not very clear on that, but it is
pretty obvious from the script itself.
Okay, I used
On 07/24/2012 10:32 PM, Juan Zhao wrote:
Therefore I suggest that the sample client work as proposed, and only
prevent that point from being obscured.
Do you mean, avoiding the places where it could triger the drag to be
obscured?
I mean only the point that is clicked. It avoids *one* place
35 matches
Mail list logo
