> A big problem with just saying "the game must use the joystick api" is that
> the game won't work on a machine without a joystick unless the joystick api
> is emulated for the mouse. This seems to me to be exactly the same problem
> and requiring exactly the same solutions, except you have moved
On 04/17/2015 05:16 AM, Carlos Garnacho wrote:
Let's expand on that example, maybe far-streched, but certainly possible:
- I'm manipulating a client window with 2 fingers on the touchscreen
(say zooming an image)
- Any other interaction on the client makes it pop up an xdg_popup
(say a third tou
On 04/16/2015 07:51 PM, x414e54 wrote:
Hi,
I am wondering if there has been any recent progress on the stability of
the Wayland relative pointer API?
I had a few ideas on the original December implementation:
Whilst we definitely need the relative event support, I feel that the
client should
On Tue, 14 Apr 2015 10:27:48 -0500
Derek Foreman wrote:
> On 14/04/15 01:38 AM, Giulio Camuffo wrote:
> > 2015-04-14 6:33 GMT+03:00 Derek Foreman :
> >> On 13/04/15 07:31 PM, Daniel Stone wrote:
> >>> Hi,
> >>>
> >>> On 14 April 2015 at 01:02, Bryce Harrington wrote:
> For purposes of discu
On Mon, 13 Apr 2015 22:33:45 -0500
Derek Foreman wrote:
> On 13/04/15 07:31 PM, Daniel Stone wrote:
> > Hi,
> >
> > On 14 April 2015 at 01:02, Bryce Harrington wrote:
> >> I had hoped to discuss collaboration on testing, but without specifics
> >> there didn't seem to be strong interest. One
On 17 April 2015 at 14:16, Carlos Garnacho wrote:
> Hey Jonas,
>
> This is drifting a bit off the topic of the original thread, better to
> spin this off. I'll reply to the DnD bits in another email.
>
> On Fri, Apr 17, 2015 at 9:50 AM, Jonas Ådahl wrote:
>> On Thu, Apr 16, 2015 at 12:55:31PM +02
Hey Michal,
On Fri, Apr 17, 2015 at 4:27 PM, Michal Suchanek wrote:
>> Nothing prevents wayland compositors today from undoing grabs when
>> clients get destroyed, or surfaces don't respond to pings. Affecting
>> this proposal, the pointer should re-enter the surface underneath and
>> keyboard
On 17 April 2015 at 16:15, Carlos Garnacho wrote:
> Hey Michal,
>
> On Fri, Apr 17, 2015 at 2:47 PM, Michal Suchanek wrote:
>
>
>>> In the X11 world, this would roughly be a Virtual Core
>>> Pointer+Keyboard grab (not that touch and active grabs are trouble
>>> free in X11, but...), GTK+ for exa
On Fri, 17 Apr 2015 19:14:30 +0900
x414e54 wrote:
> If the compositor can handle this by creating its own evdev device fd
> then having the client use libinput to receive the raw relative mouse
> motion events and dpi information then this seems a very acceptable
> solution. I am not sure though
Hey Michal,
On Fri, Apr 17, 2015 at 2:47 PM, Michal Suchanek wrote:
>> In the X11 world, this would roughly be a Virtual Core
>> Pointer+Keyboard grab (not that touch and active grabs are trouble
>> free in X11, but...), GTK+ for example does grab both devices on every
>> of those grabbing plac
On Fri, Apr 17, 2015 at 4:55 PM, Benjamin Tissoires
wrote:
> Hi Vasily,
Hi Benjamin,
> So maybe the X230t has a slightly different touchpad. I don't recall
> having any difficulties with the new patch series.
> I think I'll just revert to the v1 settings. But if you can try to
> tune the paramet
On 17 April 2015 at 14:37, Hans de Goede wrote:
> Hi,
>
>
> On 17-04-15 13:17, Michal Suchanek wrote:
>>
>> On 17 April 2015 at 12:52, Hans de Goede wrote:
>>>
>>> Hi,
>>>
>>>
>>> On 17-04-15 11:47, Michal Suchanek wrote:
On 17 April 2015 at 09:11, Pekka Paalanen wrote:
>
Hi Vasily,
On Fri, Apr 17, 2015 at 2:47 AM, Vasily Khoruzhick wrote:
> Hi Benjamin,
>
> On Thu, Apr 16, 2015 at 9:41 PM, Benjamin Tissoires
> wrote:
>> So here is a v2 (well v3 to keep things incrementing) of the x230 touchpad
>> series.
>>
>> The touchpad seems almost as fast as any other by mu
From: Pekka Paalanen
Pass 'this' weston_surface as the data argument to
weston_surface::destroy_signal listeners. The old &surface->resource was
really just an offsetted pointer to the weston_surface anyway. And,
because 'resource' happened to be the first member in struct weston_surface,
it was
From: Pekka Paalanen
There is no valid case, where you would actually destroy a
weston_surface, while leaving the wl_surface protocol object in
existence. Therefore, inert wl_surface objects do not exist, except
because of bugs.
To catch such bugs, check that the resource is really NULL before
a
On 17 April 2015 at 14:16, Carlos Garnacho wrote:
> Hey Jonas,
>
> This is drifting a bit off the topic of the original thread, better to
> spin this off. I'll reply to the DnD bits in another email.
>
> On Fri, Apr 17, 2015 at 9:50 AM, Jonas Ådahl wrote:
>> On Thu, Apr 16, 2015 at 12:55:31PM +02
Hi,
On 17-04-15 13:17, Michal Suchanek wrote:
On 17 April 2015 at 12:52, Hans de Goede wrote:
Hi,
On 17-04-15 11:47, Michal Suchanek wrote:
On 17 April 2015 at 09:11, Pekka Paalanen wrote:
On Fri, 17 Apr 2015 13:43:11 +0900
x414e54 wrote:
Thank you for the comments.
I do have a few c
Hey Jonas,
This is drifting a bit off the topic of the original thread, better to
spin this off. I'll reply to the DnD bits in another email.
On Fri, Apr 17, 2015 at 9:50 AM, Jonas Ådahl wrote:
> On Thu, Apr 16, 2015 at 12:55:31PM +0200, Carlos Garnacho wrote:
>> Hey Jonas,
>>
>> On Thu, Apr 16,
On 17 April 2015 at 12:52, Hans de Goede wrote:
> Hi,
>
>
> On 17-04-15 11:47, Michal Suchanek wrote:
>>
>> On 17 April 2015 at 09:11, Pekka Paalanen wrote:
>>>
>>> On Fri, 17 Apr 2015 13:43:11 +0900
>>> x414e54 wrote:
>>>
Thank you for the comments.
I do have a few counterpoints but I
Hi,
On 17-04-15 11:47, Michal Suchanek wrote:
On 17 April 2015 at 09:11, Pekka Paalanen wrote:
On Fri, 17 Apr 2015 13:43:11 +0900
x414e54 wrote:
Thank you for the comments.
I do have a few counterpoints but I will leave after that.
Not sure an IR/laser/wii mote pointer should even be con
Yes thank you for the comments.
I have added a bug/enhancement report related to dealing with this
from the evdev fd or libinput side. I do not have a huge amount of
time so please feel free to re-word it if you think of a better way.
If the compositor can handle this by creating its own evdev d
On 17 April 2015 at 09:11, Pekka Paalanen wrote:
> On Fri, 17 Apr 2015 13:43:11 +0900
> x414e54 wrote:
>
>> Thank you for the comments.
>> I do have a few counterpoints but I will leave after that.
>>
>> >
>> > Not sure an IR/laser/wii mote pointer should even be considered a
>> > "relative" poin
On Thu, Apr 16, 2015 at 12:55:31PM +0200, Carlos Garnacho wrote:
> Hey Jonas,
>
> On Thu, Apr 16, 2015 at 10:15 AM, Jonas Ådahl wrote:
>
>
>
> >
> > I'd have to agree on that it doesn't seem like the best thing to let the
> > compositor choose the preferred action. Having it apply compositor
>
Hi,
On 17-04-15 05:00, Peter Hutterer wrote:
On Thu, Apr 16, 2015 at 10:00:45AM +0200, Hans de Goede wrote:
Hi,
On 16-04-15 07:04, Peter Hutterer wrote:
Once we have a doubletap, enter a loop in the state machine where we can tap
multiple times and either get a multi-click or a multi-click dr
On Fri, 17 Apr 2015 13:43:11 +0900
x414e54 wrote:
> Thank you for the comments.
> I do have a few counterpoints but I will leave after that.
>
> >
> > Not sure an IR/laser/wii mote pointer should even be considered a
> > "relative" pointer since they operate in absolute coordinates. Given
> > th
25 matches
Mail list logo
