On Sat, May 12, 2012 at 01:16:38PM +0300, Pekka Paalanen wrote:
[snip]
> > Another drawback of Wayland is, that the compositor is also
> > responsible for reading and dispatching input events. If there's
> > a new class of input device _all_ compositors must be adjusted.
> > You could of course i
On 2012/5/15 23:13, Kristian Høgsberg wrote:
On Tue, May 15, 2012 at 03:17:54PM +0800, Shuang He wrote:
Hi, all
Have you met issue that, only updating wayland while not
rebuilding weston, mesa, it will not work. It may due to wayland
protocol is updated, which will need to update weston and
This way, we don't have to use wl_fixed_to_int() for
each call to weston_output_update_zoom(). The instance
in notify_motion() was missed, which broke zoom.
---
src/compositor.c |3 +++
src/shell.c |4 +---
2 files changed, 4 insertions(+), 3 deletions(-)
diff --git a/src/compositor.
On 05/15/2012 10:43 AM, Bill Spitzak wrote:
> It really sounds like the compositor should do this. IMHO it should
> produce *lots* of input events, so these gestures can be recognized.
> It would produce scroll events or whatever at the correct speed (or
> with a 24_8 increment on each) so th
It really sounds like the compositor should do this. IMHO it should
produce *lots* of input events, so these gestures can be recognized.
It would produce scroll events or whatever at the correct speed (or
with a 24_8 increment on each) so that the acceleration is exactly the
same if the cli
From: Rob Bradford
Using the surface enter/leave events track which outputs the window is on and
store those in a "window_output_list" on the window.
To create this list we define a struct window_output that is the list
relationship between the window and the output.
---
clients/window.c | 53
On Tue, May 15, 2012 at 5:20 PM, Chase Douglas
wrote:
> The real issue is when you want to have object manipulation within an
> application. Let's take smooth scrolling using a trackpad as an example.
> One approach would be to use the same acceleration for scrolling as for
> cursor motion. Scroll
On Tue, May 15, 2012 at 04:14:47PM +0300, Ander Conselvan de Oliveira wrote:
> The type of fields x and y in wl_input_device was changed to wl_fixed_t
> but input_device_attach() was still using it as if it were integer.
> This bug caused the pointer sprite to be configured in the wrong place
> on
On Tue, May 15, 2012 at 02:32:05PM +0300, Ander Conselvan de Oliveira wrote:
> notify_motion() now receives coordinates in wl_fixed_t but the test was
> still passing integers.
Thanks, committed.
Kristian
> ---
> tests/event-test.c |3 ++-
> 1 files changed, 2 insertions(+), 1 deletions(-)
>
On Tue, May 15, 2012 at 10:29:12AM +0300, Pekka Paalanen wrote:
> I was just curious of how much the looping takes time without
> conversion, so I added this.
>
> My results on Intel(R) Core(TM) i5-2410M CPU @ 2.30GHz:
>
> benchmarked noop: 1.876349827s
> benchmarked magic:2.245844470s
>
On 05/15/2012 02:00 AM, Jonas Ådahl wrote:
> On Mon, May 14, 2012 at 7:31 PM, Chase Douglas
> wrote:
>> On 05/09/2012 02:31 PM, Jonas Ådahl wrote:
>>> Touchpad related code has been rewritten and moved to its own file
>>> accessed by evdev via the dispatch interface.
>>>
>>> The various functional
On Tue, May 15, 2012 at 03:17:54PM +0800, Shuang He wrote:
> Hi, all
> Have you met issue that, only updating wayland while not
> rebuilding weston, mesa, it will not work. It may due to wayland
> protocol is updated, which will need to update weston and mesa as
> well.
> Is there any proto
On Tue, May 15, 2012 at 09:21:37AM +0300, Pekka Paalanen wrote:
> On Mon, 14 May 2012 14:39:39 -0400
> Kristian Høgsberg wrote:
>
> > On Mon, May 14, 2012 at 9:59 AM, Kristian Høgsberg
> > wrote:
> > > On Mon, May 14, 2012 at 02:01:50PM +0300, Pekka Paalanen wrote:
> > >> Toytoolkit clients wil
On Mon, May 14, 2012 at 04:41:10PM -0400, Darxus wrote:
> Haven't figured out how to regenerate the html, so it's not tested.
> Looks like remaining html errors will be fixed in the next publican
> release: https://bugzilla.redhat.com/show_bug.cgi?id=788576
Thanks, applied, and I updated the onli
The type of fields x and y in wl_input_device was changed to wl_fixed_t
but input_device_attach() was still using it as if it were integer.
This bug caused the pointer sprite to be configured in the wrong place
on the screen (usually outside the visible area) but it would soon be
corrected in notif
notify_motion() now receives coordinates in wl_fixed_t but the test was
still passing integers.
---
tests/event-test.c |3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/tests/event-test.c b/tests/event-test.c
index 737e227..e89d5aa 100644
--- a/tests/event-test.c
+++ b/tes
On Tue, May 15, 2012 at 5:38 AM, Juan Zhao wrote:
> **
> Hi All,
>
> I've successfully run weston and its shm and egl/gles client over
> Intel CE platform SDV now.
> The code can be accessed on
> https://gitorious.org/wayland-and-weston-with-gdlbackend . The main code
> is just compos
On Thu, May 10, 2012 at 10:59:17PM +0100, Daniel Stone wrote:
> Hi,
>
> On 10 May 2012 22:11, Kristian Høgsberg wrote:
> > I agree that we need to get evdev a little more under control, but I
> > was thinking that we'd be able to decide up front that a device is a
> > touchpad, a mouse a keyboard
On Thu, May 10, 2012 at 07:13:09PM +0100, Daniel Stone wrote:
> Hi,
>
> On 10 May 2012 17:45, Christopher James Halse Rogers
> wrote:
> > Is Weston going to essentially fold in all the interesting bits from all
> > the input DDXs to the core (and require this to be duplicated in all
> > other com
On Mon, May 14, 2012 at 7:31 PM, Chase Douglas
wrote:
> Can we move the acceleration code to a library? The reason I ask is that
> we will want acceleration to feel the same whether the display server or
> a client wants to move objects.
Yep, I think this is a good point.
It avoids repeating the
On Wed, May 9, 2012 at 11:31 PM, Jonas Ådahl wrote:
> Touchpad related code has been rewritten and moved to its own file
> accessed by evdev via the dispatch interface.
>
> The various functionality implemented are anti-flicker (don't jumping
> around), smoother motions, touch detection, pointer a
On Mon, May 14, 2012 at 7:31 PM, Chase Douglas
wrote:
> On 05/09/2012 02:31 PM, Jonas Ådahl wrote:
>> Touchpad related code has been rewritten and moved to its own file
>> accessed by evdev via the dispatch interface.
>>
>> The various functionality implemented are anti-flicker (don't jumping
>> a
I was just curious of how much the looping takes time without
conversion, so I added this.
My results on Intel(R) Core(TM) i5-2410M CPU @ 2.30GHz:
benchmarked noop: 1.876349827s
benchmarked magic: 2.245844470s
benchmarked div:12.709085309s
benchmarked mul:7.504838141s
Hi, all
Have you met issue that, only updating wayland while not rebuilding
weston, mesa, it will not work. It may due to wayland protocol is
updated, which will need to update weston and mesa as well.
Is there any protocol version check policy applied? I'd like to be
told that 'protoco
24 matches
Mail list logo
