Hi folks,
for my master thesis in computer science I am looking into implementing
a wayland-compositor for eink devices (specifically for a Kobo Glo
Reader I own). For the record I am currently only looking into it, so
no promises ;)
Someone from the mobileread forum already implemented a open s
On Mon, 10 Jun 2013 14:40:19 -0300
"Eduardo Lima (Etrunko)" wrote:
> On 06/07/2013 11:01 AM, Pekka Paalanen wrote:
> > On Mon, 3 Jun 2013 12:24:09 -0300
> > "Eduardo Lima (Etrunko)" wrote:
> >
> >> From: "Eduardo Lima (Etrunko)"
> >>
> >> These can be used by external clients to check the ins
On Mon, Jun 10, 2013 at 12:34 PM, Bill Spitzak wrote:
> Pekka Paalanen wrote:
>
>>> If a client does nothing after an enter event it will get the system
>>> cursor.
>>
>>
>> That would cause cursor flicker. Btw this is a suggestion, right?
>> Because this is not what the current implementation doe
---
clients/editor.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/clients/editor.c b/clients/editor.c
index df82ed0..6f1f747 100644
--- a/clients/editor.c
+++ b/clients/editor.c
@@ -1155,11 +1155,13 @@ key_handler(struct window *window,
wid
---
clients/editor.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/clients/editor.c b/clients/editor.c
index d4e4e92..df82ed0 100644
--- a/clients/editor.c
+++ b/clients/editor.c
@@ -946,8 +946,8 @@ text_entry_draw_cursor(struct text_entry *entry, cairo_t
*cr)
Martin Minarik wrote:
* The client are perhaps more interested in knowing which keys changed,
not what is the actual state. Delivering state is less flexible because
it requires the client to keep track of state, if it wants to know what
changed. But the compositor knows what changed. Clie
Are you really saying the event is "these are the buttons that have
changed state since you last got an event?". That seems a nightmare for
the compositor to keep track of (it has to remember the last button
state for every client).
If instead this is just a report of the current state, then t
This is going to be used by compositor for the following use cases:
* Hot plugging/unplugging an input device with already held keys.
* Handling an input lag gracefully.
However, for backward compatibility, the wl_keyboard.enter()
still uses the keys array, not using this method in that case.
Th
Pekka Paalanen wrote:
If a client does nothing after an enter event it will get the system
cursor.
That would cause cursor flicker. Btw this is a suggestion, right?
Because this is not what the current implementation does. In the
current Wayland protocol, the cursor is undefined on enter, and
Extend the wl_pointer protocol, to enable:
* Hot plugging/unplugging an input device with already held keys.
* Handling an input lag gracefully.
* Provide a way to deliver the state of all buttons when focusing a surface.
---
protocol/wayland.xml | 34 +-
1 file c
I've been poking at XWayland+Weston's XWM recently and wanted to find this
behavior and check that this patch is effective so I could vouch for it, but
I haven't seen something that looks like windows being mapped with the wrong
coordinates or size. Louis-Francis, could you explain how to reproduce
> -Original Message-
> From: wayland-devel-bounces+kwangwoong.lee=lge@lists.freedesktop.org
> [mailto:wayland-devel-bounces+kwangwoong.lee=lge@lists.freedesktop.org]
> On Behalf Of Pekka Paalanen
> Sent: Sunday, June 09, 2013 11:03 PM
> To: Elvis Lee (__)
> Cc: wayland-devel@lis
On 06/07/2013 11:01 AM, Pekka Paalanen wrote:
> On Mon, 3 Jun 2013 12:24:09 -0300
> "Eduardo Lima (Etrunko)" wrote:
>
>> From: "Eduardo Lima (Etrunko)"
>>
>> These can be used by external clients to check the installation path
>>
>> Signed-off-by: Eduardo Lima (Etrunko)
>> ---
>> src/weston.p
On Fri, 7 Jun 2013 16:52:45 +0300
Ander Conselvan de Oliveira
wrote:
> The fix to not call glTexImage2D() on every attach does not properly
> set the texture damage region appropriately when the surface has a
> buffer transform with 90 or 270 degrees rotation, since it would
> simply multiply the
On Mon, 10 Jun 2013 09:31:22 -0700
Bill Spitzak wrote:
> On 06/09/2013 11:02 PM, Pekka Paalanen wrote:
>
> >> Is this approach possible? I want to listen your opinions.
> >
> > Hi Elvis,
> >
> > do I understand right, that you would like to add the concept of a
> > system cursor?
> >
> > I guess
On 06/10/2013 03:18 AM, Pekka Paalanen wrote:
On Fri, 7 Jun 2013 17:13:59 +0200
Marc Chalain wrote:
+cmap->start = 0;
+cmap->len = cols;
+cmap->red = colors;
+cmap->blue = colors;
+cmap->green = colors;
If there actually is a difference between rcols, gcols, and bcols,
s
On 06/09/2013 11:02 PM, Pekka Paalanen wrote:
Is this approach possible? I want to listen your opinions.
Hi Elvis,
do I understand right, that you would like to add the concept of a
system cursor?
I guess it would be possible, but why?
It seems the system cursor you propose would be one arb
Hi,
--- a/src/Makefile.am
> +++ b/src/Makefile.am
> @@ -94,7 +94,6 @@ westoninclude_HEADERS = \
> ../shared/matrix.h \
> ../shared/config-parser.h
>
> -moduledir = $(libdir)/weston
> module_LTLIBRARIES =
From: Rob Bradford
---
man/weston.ini.man | 8
1 file changed, 8 insertions(+)
diff --git a/man/weston.ini.man b/man/weston.ini.man
index c3e5747..93bd982 100644
--- a/man/weston.ini.man
+++ b/man/weston.ini.man
@@ -288,6 +288,14 @@ be one of the following 8 strings:
.BR "flipped-270
From: Rob Bradford
---
src/compositor-drm.c | 16
src/compositor.h | 2 ++
src/input.c | 2 ++
src/udev-seat.c | 3 +++
4 files changed, 23 insertions(+)
diff --git a/src/compositor-drm.c b/src/compositor-drm.c
index 76d0810..7d33977 100644
--- a/src/compos
From: Rob Bradford
Centre the pointer on a the provided output. This function provides the
basis of ensuring that the pointer starts on the output when we start to
constrain a seat to a given output.
---
src/compositor.h | 3 +++
src/input.c | 8
2 files changed, 11 insertions(+)
From: Rob Bradford
This change spills the code for looking up a seat by name and then
potentially creating it if it doesn't exist into a new function called
udev_seat_get_named.
This change allows us to reuse this code when looking up the seat
when parsing seat constraints per output.
---
src/u
On Fri, 7 Jun 2013 12:39:21 +0200
Marc Chalain wrote:
> this patch use the "idle-time" entry inside the "core" section of
> weston.ini to set the named value.
Hi Marc,
does this actually work?
I think the backend init calls weston_compositor_init(), where your
code then loads the idle-time fro
On Mon, 10 Jun 2013 12:18:57 +0200
Marc Chalain wrote:
> Linux kernel uses a lot of function pointers. And I'm looking this solution.
Please, do not use function pointers here, that would be just an
additional layer of indirection for no benefit, I believe.
Also, reply after the quote, please.
Linux kernel uses a lot of function pointers. And I'm looking this solution.
2013/6/10 Pekka Paalanen
> On Mon, 10 Jun 2013 09:47:32 +0200
> Marc Chalain wrote:
>
> > Hi Pekka,
> > I agree with --disable-multitouch.
> > For the comparison between the use of ifdef and no-op functions. I think
>
On Fri, 7 Jun 2013 17:13:59 +0200
Marc Chalain wrote:
> From e30486e0288e7be526fc358a5318b344522e407b Mon Sep 17 00:00:00 2001
> From: mchalain
> Date: Fri, 7 Jun 2013 17:12:31 +0200
> Subject: [PATCH] [fbdev_backend]: support of DIRECTCOLOR Frame buffer
>
A properly formatted title:
c
On Mon, 10 Jun 2013 09:47:32 +0200
Marc Chalain wrote:
> Hi Pekka,
> I agree with --disable-multitouch.
> For the comparison between the use of ifdef and no-op functions. I think
> the second solution is ambiguous, we disable the feature in one side and we
> use the API in the other side.
> I loo
Ok I will try to write a better commit message.
But for frame buffer understanding, the buffer is often allowed for a
screen with the double of height as showed. Then is possible to set the
buffer with two screens, one above the other. After we switch the display
from the first middle buffer to the
On Fri, 7 Jun 2013 17:20:23 +0200
Marc Chalain wrote:
> From 6553ed3ad9845113f3b2280e6fc94e2b326a7eca Mon Sep 17 00:00:00 2001
> From: mchalain
> Date: Fri, 7 Jun 2013 17:18:23 +0200
> Subject: [PATCH 2/2] [fbdev_backend] initialization of the first frame
> buffer
>
> ---
> src/compositor-fbde
Hi Pekka,
I agree with --disable-multitouch.
For the comparison between the use of ifdef and no-op functions. I think
the second solution is ambiguous, we disable the feature in one side and we
use the API in the other side.
I look if it's possible to have a third solution which satisfies every
bod
30 matches
Mail list logo
