Hi,
> michael.blumenkra...@gmail.com wrote:
>
> [...]
>
> To echo Jonas's comments, I'm also strongly opposed to adding window
stacking
> manipulation to the xdg-shell protocol. It's already a mess handling
windows
> which try to raise/focus themselves in X11, this is not an issue I want to
> hand
libinput 1.5.3 is now availabl with three bug fixes:
* the HP Pavilion DM4 has a quirk added to disable (jumpy) multitouch events
* the calibration matrix udev property is now parsed for the path backend
(and parsed in a locale-independent manner)
* we now sync the BTN_TOOL_FINGER state on init.
Hi Eric,
The problem here is we are using crtc_id and connector_id as indexes,
while they aren't.
Nothing keeps DRM drivers from advertising CRTC and connectors with ids
that aren't sequential and starting at 0 or 1.
The right fix is to use indexes instead of ids to update bitmasks.
drm_output:
On Tue, Dec 6, 2016 at 3:32 AM, Daniel Stone wrote:
> Hi,
>
> On 5 December 2016 at 03:36, Dima Ryazanov wrote:
> > (This is kind of a workaround, but perhaps the right thing to do
> anyways.)
> >
> > The menu implementation in window.c needs to know the time of the event
> that
> > triggered th
I think now the simplest way to fix cross-builder's problem is that:
When the USE_HOST_SCANNER variable is set we have to allow to redefine
wayland_scanner variable in the same way as CC or CC_FOR_BUILD. For example
by command line arguments:
WAYLAND_SCANNER_FOR_BUILD=/usr/bin/wayland-scanner *.
From: Yong Bakos
Despite their clear names, wl_array and wl_list members are undocumented,
resulting in doxygen warnings[1] when building documentation.
Document these members, suppressing the warnings.
[1] Warnings are visible when EXTRACT_ALL = NO.
Signed-off-by: Yong Bakos
---
src/wayland
Yes I fully agree that things are not perfect atm, and we want to work
towards improving things.
I'll see to "polishing" the scanner as early as possible.
Thanks
Emil
___
wayland-devel mailing list
wayland-devel@lists.freedesktop.org
https://lists.freede
Hi,
On 5 December 2016 at 03:36, Dima Ryazanov wrote:
> (This is kind of a workaround, but perhaps the right thing to do anyways.)
>
> The menu implementation in window.c needs to know the time of the event that
> triggered the menu - however, the xdg-shell's show_window_menu API does not
> give
Hi Pekka,
Thanks for the explanation. You're probably right; this shouldn't be
possible.
I haven't been able to reproduce the bug again. The one time I got it was
when I was working on my show_window_menu patches - so it's quite possible
that something there was causing it. (In fact, the window m