| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Needed for apps to support overscroll on the Mac.
|
|
|
|
| |
I followed the steps of @mneumann.
|
|\
| |
| | |
support utf8 window titles via _NET_WM_NAME standard
|
| |
| |
| |
| | |
…instead of low-level X11 calls that don't work with utf8
|
| |
| |
| |
| |
| |
| |
| | |
based on this freerdp patch
https://github.com/FreeRDP/FreeRDP/commit/9767f7f042a58aae876e0ad3b2e7bde356c8fda9
thanks to emiliocobos on irc
|
|/
|
|
| |
Part of servo/servo#8641
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fixes #697
It seems that `XSync` doesn't really makes the window viewable.
This feels hacky, other option to do it could be using `XIfEvent` or
similar to listen to `MapNotify` events, but we'll have a loop still.
In practice, this lasts between two and thre iterations on my machine,
which is something not noticeable.
|
|\
| |
| | |
x11: Prevent leak on XIQueryDevice
|
| |
| |
| |
| |
| |
| |
| | |
Per http://linux.die.net/man/3/xiquerydevice:
> XIFreeDeviceInfo frees the information returned by
> XIQueryDevice.
|
|/ |
|
| |
|
| |
|
| |
|
| |
|
|\
| |
| | |
Minimum/maximum dimensions for windows in win32 API
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Regression introduced in 47df0e9eaa7f1231a07f86fc44426936c7a2589a
Casting fullscreen_atom (which is the result from XInternAtom, i.e.
c_ulong) as i64 is obviously wrong -- the whole point of types such as
c_ulong is that long in C does *not* always have the same bit size...
Cast it as c_long instead.
While this is the most straightforward fix, I'm not sure it's the best
one: perhaps the x11 crate should offer a set_ulong() method along with
set_long(), which could be used here instead of the cast?
|
|\ \
| |/
|/| |
Fix fullscreen on X11
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
We were previously allowing only fullscreen modes which were exactly as
tall as the requested dimensions, perhaps erroneously.
|
| | |
|
| | |
|
| |
| |
| |
| | |
Focusing the newly created window seems to grab the keyboard.
|
| |
| |
| |
| |
| | |
I switched `vsyncstart` and `vdisplay` again, as per the discussion on
issue #582.
|
| | |
|
|/ |
|
|
|
|
|
| |
* If `multitouch` is enabled, touch input generates touch events.
* If `multitouch` is disabled, touch input generates emulated mouse events.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|\
| |
| | |
Fix smooth-scrolling increment on some X11 devices
|
| |
| |
| |
| |
| | |
When multiple scrolling devices are attached, XIAllMasterDevices does not
include the scroll axes for all hardware devices.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
From the "Smooth Scrolling" section of [XI2Proto.txt][1]:
> One unit of scrolling in either direction is considered to be equivalent to
> one button event, e.g. for a unit size of 1.0, -2.0 on an valuator type
> Vertical sends two button press/release events for button 4. Likewise, a
> button press event for button 7 generates an event on the Horizontal
> valuator with a value of +1.0. The server may accumulate deltas of less than
> one unit of scrolling.
From [What's new in XI 2.1 - smooth scrolling][2]:
> The increment defines what delta the driver considers to be one scroll
> event. For an increment of +5, each delta of 5 should be regarded as one
> scroll unit down. For an increment of -3, each delta of 3 should be regarded
> as one scroll unit up (i.e. inverted).
[1]: http://www.x.org/releases/X11R7.7/doc/inputproto/XI2proto.txt
[2]: http://who-t.blogspot.com/2011/09/whats-new-in-xi-21-smooth-scrolling.html
This fixes scrolling with my Microsoft mouse in X11 on Debian 8.1.
|
| |
| |
| |
| | |
Tested on DragonFly BSD. Should work similarily on FreeBSD.
|
|/
|
|
|
| |
KeymapNotify should not be handled by calling XRefreshKeyboardMapping.
XRefreshKeyboardMapping expects XMappingEvent.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
fixes #314 for me.
I've "tested" change by running examples (which prior to change simply
crashed), but since I did not run those examples successfuly ever before,
I don't know whether they worked as intended.
|