Relying only on maximized/fullscreen states to do tiling or hiding
decorations feels bit nasty, as for client developers it's documented
that fullscreen and maximized are indeed what they are. For example
fullscreen application such as video player could hide controls in
fullscreen mode, which is
On Tue, 5 Aug 2014 22:07:39 +0300
Jari Vetoniemi mailro...@gmail.com wrote:
Rationale for this patch is to provide way for applications that can't go
below/above
certain bounds to inform compositor about it.
More feedback is needed. For example are maximimum size useful for any
On Fri, 18 Jul 2014 11:05:03 +0200
Marek Chalupa mchqwe...@gmail.com wrote:
On 17 July 2014 19:54, Jasper St. Pierre jstpie...@mecheye.net wrote:
This allows compositors to easily select a good display to listen on.
---
src/wayland-server.c | 97
On Thu, 17 Jul 2014 13:54:21 -0400
Jasper St. Pierre jstpie...@mecheye.net wrote:
We'll use this to autodetect a good socket to open on.
---
src/wayland-server.c | 41 ++---
1 file changed, 26 insertions(+), 15 deletions(-)
On Wed, 6 Aug 2014 11:21:59 +0200
Marek Chalupa mchqwe...@gmail.com wrote:
When some function during adding socket fails, it must clean
everything it set or we can get funky errors.
This patch fixes:
http://lists.freedesktop.org/archives/wayland-devel/2014-August/016331.html
On Wed, 6 Aug 2014 11:28:34 +0200
Marek Chalupa mchqwe...@gmail.com wrote:
If the malloc fails, memset would touch invalid memory.
---
src/wayland-server.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/src/wayland-server.c b/src/wayland-server.c
index
On Thu, 7 Aug 2014 15:41:10 +0300
Pekka Paalanen ppaala...@gmail.com wrote:
On Thu, 17 Jul 2014 13:54:21 -0400
Jasper St. Pierre jstpie...@mecheye.net wrote:
We'll use this to autodetect a good socket to open on.
---
src/wayland-server.c | 41 ++---
On Wed, 06 Aug 2014 11:51:26 +0200
Jonny Lamb jonny.l...@collabora.co.uk wrote:
On mer, 2014-08-06 at 11:50 +0200, Jonny Lamb wrote:
- if (shseat-seat-pointer-grab_serial == shsurf-popup.serial) {
+ if (shseat-seat-pointer
+ shseat-seat-pointer-grab_serial ==
On Wed, 6 Aug 2014 12:18:12 +0200
Marek Chalupa mchqwe...@gmail.com wrote:
The only value that is false with the former condition is 0.
On error we set fd to -1.
---
src/wayland-server.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/src/wayland-server.c
From: Pekka Paalanen pekka.paala...@collabora.co.uk
0 is also a valid fd, and needs to be closed.
On error we set fd to -1. We need to also initialize fds to -1, so we do
not accidentally close stdout on error.
While fixing this, also remove one use-before-NULL-check.
Based on the patch by
The idea here was that once upon a time, clients could rebind wl_display
to a higher version, so we offered the ability to rebind it
here. However, this is particularly broken. The existing bind
implementation actually still hardcodes version numbers, and it leaks
previous resources, overwriting
Reviewed-by: Jasper St. Pierre jstpie...@mecheye.net
On Thu, Aug 7, 2014 at 9:51 AM, Pekka Paalanen ppaala...@gmail.com wrote:
From: Pekka Paalanen pekka.paala...@collabora.co.uk
0 is also a valid fd, and needs to be closed.
On error we set fd to -1. We need to also initialize fds to -1,
What is the default value of these hints?
I would propose -1 as default, meaning unset.
Compositor has to deal with not knowing the minimum size, preferably
this would mean though that the client can be set to any valid size.
When is the client expected to send this? Can this be sent before
Sorry for not posting to the ML, but this looked good so I pushed it.
--Jason
On Thu, Jul 17, 2014 at 10:54 AM, Jasper St. Pierre jstpie...@mecheye.net
wrote:
This patch series introduces a new API to find an open Wayland display
so that compositors don't need to reimplement all this code.
On Wed, Aug 6, 2014 at 1:31 AM, Marek Chalupa mchqwe...@gmail.com wrote:
Hi,
After the new patches for socket automatic naming the socket test, namely
socket_path_overflow_server_create, fails. Probably introduced in
79b1d2039aeb77b712cf4e1bb4049ebf9c453b59. It does not set errno as
On 08/07/2014 07:18 AM, Jari Vetoniemi wrote:
What is the default value of these hints?
I think you could get away with defaulting the minimum to be about
100x100. I think that is sufficient to get clients to work ok and it is
small enough to encourage them to set this rather than relying on
---
src/screenshooter.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/src/screenshooter.c b/src/screenshooter.c
index 9ae0d29..4403933 100644
--- a/src/screenshooter.c
+++ b/src/screenshooter.c
@@ -265,6 +265,7 @@ bind_shooter(struct wl_client *client,
if (client != shooter-client)
An error makes the client exit, which cleans up the resources anyway.
---
desktop-shell/input-panel.c | 1 -
desktop-shell/shell.c | 2 --
src/screenshooter.c | 1 -
src/text-backend.c | 2 --
4 files changed, 6 deletions(-)
diff --git a/desktop-shell/input-panel.c
To make our code more clear.
---
src/compositor.c | 4 ++--
src/input.c | 2 +-
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/src/compositor.c b/src/compositor.c
index 55c959e..4d6a02a 100644
--- a/src/compositor.c
+++ b/src/compositor.c
@@ -3145,7 +3145,7 @@
With tablets that don't support serial numbers, we can't guarantee that the tool
objects are unique. Because of this, this can give clients the false impression
that a tool without a serial number is being shared between tablets when it very
well might not be. So we keep tools without serial
With tablets that don't support serial numbers, we can't guarantee that the tool
objects are unique. Because of this, this can give clients the false impression
that a tool without a serial number is being shared between tablets when it very
well might not be. So we keep tools without serial
On Thu, Aug 07, 2014 at 07:00:52PM -0400, Stephen Chandler Paul wrote:
With tablets that don't support serial numbers, we can't guarantee that the
tool
objects are unique. Because of this, this can give clients the false
impression
that a tool without a serial number is being shared between
On Thu, Aug 07, 2014 at 06:54:55PM -0400, Stephen Chandler Paul wrote:
Because the axes that tool reports can change depending on the tool in use, we
want to be able to provide functionality to determine which axes each tool can
support.
Signed-off-by: Stephen Chandler Paul
Because the axes that tool reports can change depending on the tool in use, we
want to be able to provide functionality to determine which axes each tool can
support.
Signed-off-by: Stephen Chandler Paul thatsly...@gmail.com
---
= Changes =
* Fixed the line width in test/tablet.c
*
On Thu, Aug 07, 2014 at 10:02:22PM -0400, Stephen Chandler Paul wrote:
Because the axes that tool reports can change depending on the tool in use, we
want to be able to provide functionality to determine which axes each tool can
support.
Signed-off-by: Stephen Chandler Paul
We had reports that the top software button area is hard to hit for those
using the trackpoint and clicking the buttons with their thumb.
Analysis of event recordings (3 different people) for left, right and middle
clicks shows that there is a significant amount of events up to about 10mm
(with
26 matches
Mail list logo
