On Sun, 9 Feb 2014 21:35:10 -0800
Kristian Høgsberg hoegsb...@gmail.com wrote:
On Sat, Feb 08, 2014 at 11:44:11AM +0200, Pekka Paalanen wrote:
On Fri, 7 Feb 2014 22:27:00 -0800
Kristian Høgsberg k...@bitplanet.net wrote:
On the client side we log fatal errors before we exit. If a
On Mon, Feb 10, 2014 at 03:13:55PM +1000, Peter Hutterer wrote:
On Thu, Feb 06, 2014 at 10:27:54PM +0100, Jonas Ådahl wrote:
Since a Wayland compositor have to represent all touch devices of a seat
as one virtual device, lets make that easier by making the slots of
touch events seat wide
On Mon, Feb 10, 2014 at 03:44:56PM +1000, Peter Hutterer wrote:
If we don't have capabilities we can deal with, return a different
error so the backends can handle it separately (they already do).
Looks good to me.
Jonas
Signe-off-by: Peter Hutterer peter.hutte...@who-t.net
---
On Mon, Feb 10, 2014 at 10:11:47AM +0100, Jonas Ådahl wrote:
On Mon, Feb 10, 2014 at 03:13:55PM +1000, Peter Hutterer wrote:
On Thu, Feb 06, 2014 at 10:27:54PM +0100, Jonas Ådahl wrote:
Since a Wayland compositor have to represent all touch devices of a seat
as one virtual device, lets
On Sat, 8 Feb 2014 15:23:29 -0600
Jason Ekstrand ja...@jlekstrand.net wrote:
Pekka,
First off, I think you've done a great job over-all. I think it will both
cover most cases and work well I've got a few comments below.
Thank you for the review. :-)
Replies below.
On Thu, Jan 30, 2014 at
On Mon, Feb 10, 2014 at 07:47:00PM +1000, Peter Hutterer wrote:
On Mon, Feb 10, 2014 at 10:11:47AM +0100, Jonas Ådahl wrote:
On Mon, Feb 10, 2014 at 03:13:55PM +1000, Peter Hutterer wrote:
On Thu, Feb 06, 2014 at 10:27:54PM +0100, Jonas Ådahl wrote:
Since a Wayland compositor have to
On Wed, 2014-01-29 at 18:47 +0200, Ander Conselvan de Oliveira wrote:
Remove the listener for output destroy from weston_view and instead
iterate views owned by the shell in its own output destroy listener.
This simplifies the code a bit since keeping the view listening for the
destroy on
On Sat, 8 Feb 2014 15:39:57 -0600
Jason Ekstrand ja...@jlekstrand.net wrote:
On Wed, Feb 5, 2014 at 1:32 AM, Pekka Paalanen ppaala...@gmail.com wrote:
On Thu, 30 Jan 2014 17:35:17 +0200
Pekka Paalanen ppaala...@gmail.com wrote:
Hi,
it's time for a take two on the Wayland
From: Emilio Pozuelo Monfort emilio.pozu...@collabora.co.uk
https://bugs.freedesktop.org/show_bug.cgi?id=73173
---
desktop-shell/exposay.c | 108
desktop-shell/shell.c | 7
desktop-shell/shell.h | 74 +++--
On Mon, Feb 10, 2014 at 3:53 AM, Pekka Paalanen ppaala...@gmail.com wrote:
On Sat, 8 Feb 2014 15:23:29 -0600
Jason Ekstrand ja...@jlekstrand.net wrote:
Pekka,
First off, I think you've done a great job over-all. I think it will
both
cover most cases and work well I've got a few
Hi Bill, hi Jasper, hi everybody again,
I just updated my taskbar code to make it work against Weston 1.4.0 :
https://github.com/Tarnyko/weston-taskbar/tree/1.4.0-taskbar
And with regards to our former conversation, I added a logic that allows
the client to know when it has been minimized :
2014-02-10 17:25 GMT+02:00 Manuel Bachmann
manuel.bachm...@open.eurogiciel.org:
Hi Bill, hi Jasper, hi everybody again,
I just updated my taskbar code to make it work against Weston 1.4.0 :
https://github.com/Tarnyko/weston-taskbar/tree/1.4.0-taskbar
And with regards to our former
Oh, and I forgot to add, the taskbar has its own logic asking the
compositor to hide, so clicking on the taskbar will do this, too. Sorry for
the additional noise.
Regards,
Manuel
2014-02-10 16:43 GMT+01:00 Manuel Bachmann
manuel.bachm...@open.eurogiciel.org:
Hi Guilio,
In fact, the client
The client had logic to adjust the dx/dy parameter of the window when
resizing, but it was broken: nothing enabled that code, and it would only
work for the first resize.
To make up for it, desktop-shell had code to flat out ignore the dx/dy
parameters when resizing and anchor it its own way.
Hi,
On 10 February 2014 13:23, Emilio Pozuelo Monfort poch...@gmail.com wrote:
When a view was destroyed while we were on exposay, we didn't
remove it from the list of views, and so when leaving exposay
we were trying to animate (and sometimes activate) a
non-existent view, causing a crash.
Pekka Paalanen wrote:
This algorithm aims to start showing an update between t-T/2 and t+T/2,
which means that presentation may occur a little early or late, with
an average of zero. Another option would be to show the update between
t and t+T, which would mean that presentation would be always
I need to read the rest of the responses, but this does *not* sound like
what I think is necessary. There should not be any need for an event
saying you have been minimized as this should never happen without the
client first requesting it.
As I see it, if the compositor decides to minimize
Okay this sounds like it is going in exactly the wrong direction.
What I am trying to do is restore the ability to use overlapping windows
which was broken in approximatly 1990 when everybody started doing
click raises (when even then it was *trivial* for a client to raise
it's own windows),
I would think configure request is going to need to provide this
information. Otherwise the compositor cannot do tabbed or tiled layouts
were it wants a window to resize without the client requesting it.
Then again perhaps it is ok for compositor-initiated resizing to always
produce the same
On 10/02/2014 21:57, Bill Spitzak wrote:
Okay this sounds like it is going in exactly the wrong direction.
And you sound like you do not understand the strong need here: the
compositor *must be in charge* of everything. But, please, do not start
to yell now, it can perfectly work well with
The parameter was already removed, I'm simply updating the documentation.
On Mon, Feb 10, 2014 at 4:41 PM, Bill Spitzak spit...@gmail.com wrote:
I would think configure request is going to need to provide this
information. Otherwise the compositor cannot do tabbed or tiled layouts
were it
sardemff7+wayl...@sardemff7.net wrote:
First, a compositor may have no mechanism of “minimization”, so it must
not be forced to obey such a request with no meaning for it.
I agree the compositor does not have to obey the minimize request. I
think I am not explaining things clearly: *BOTH*
(Some parts are reordered to makes more sense in my answers. Agreed
parts are removed.)
On 10/02/2014 23:42, Bill Spitzak wrote:
sardemff7+wayl...@sardemff7.net wrote:
Based on Bill’s events and requests, here is what I think should
handle all cases the right way while keeping the global
sardemff7+wayl...@sardemff7.net wrote:
Not sure why you want to limit it like this. I certainly would like
the ability to minimized dialog windows.
If you want a dialog window to be minimized, then it makes even more
sense to allow minimizing multiple surfaces. The client could want to
24 matches
Mail list logo
