| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
| |
Size hints are only being set for non-fullscreen windows, if
`max_dimensions` are set they'll override the normal `dimensions`
since X11 will not automatically resize the window after setting
the size hints.
`PSize` hint is currently set along with the `min/max` hints for
good measure.
|
|\
| |
| | |
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.
|
| |
|
| |
|
| |
|
| |
|
|\
| |
| | |
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.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
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.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
* Adding dependencies
* Replacing `i8` with `c_char` ot `_` (since `c_char` can be
unsigned on some platforms, aarch64 is one of them)
|
| |
|
|\
| |
| | |
Split creating an EGL context in two parts
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
* Fix an issue where PollEventsIterator::next() would fail to return
keyboard input and mouse events immediately but instead only
return them on the next call to next()
* Inline process_generic_event() and queue_event()
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Scroll deltas are calculated in X11 by comparing the current and
previous absolute values for the scroll axis when a scroll motion
event is received. If the user scrolls whilst the cursor is outside
of the window then an incorrect delta is reported when the cursor
re-enters the window.
Fix this by resetting the last-seen axis values whenever the cursor
re-enters the window.
|
| |
| |
| |
| |
| |
| |
| | |
* For the moment we're still using plain core X11 events
for handling keyboard activity, so remove the XInput2 code for that
* Small refactoring of X11 input handling and documentation fixes
|
|/
|
|
|
| |
This provides smooth scrolling for touchpad devices and will
enable support for touch events etc. in future.
|
| |
|