2014-07-27 18:55:37 +10:00
|
|
|
[package]
|
2016-02-23 22:56:23 +11:00
|
|
|
name = "winit"
|
2018-04-27 08:53:16 +10:00
|
|
|
version = "0.13.1"
|
2016-02-23 22:56:23 +11:00
|
|
|
authors = ["The winit contributors, Pierre Krieger <pierre.krieger1708@gmail.com>"]
|
|
|
|
|
description = "Cross-platform window creation library."
|
|
|
|
|
keywords = ["windowing"]
|
2014-11-13 19:01:30 +11:00
|
|
|
license = "Apache-2.0"
|
2014-11-14 18:54:04 +11:00
|
|
|
readme = "README.md"
|
2016-02-23 22:56:23 +11:00
|
|
|
repository = "https://github.com/tomaka/winit"
|
2016-09-20 02:53:28 +10:00
|
|
|
documentation = "https://docs.rs/winit"
|
2017-01-31 20:01:36 +11:00
|
|
|
categories = ["gui"]
|
2014-07-27 18:55:37 +10:00
|
|
|
|
2015-02-06 19:21:55 +11:00
|
|
|
[dependencies]
|
2017-12-28 04:39:38 +11:00
|
|
|
lazy_static = "1"
|
2015-11-09 18:22:48 +11:00
|
|
|
libc = "0.2"
|
2014-10-04 23:49:39 +10:00
|
|
|
|
2016-05-03 07:58:52 +10:00
|
|
|
[target.'cfg(target_os = "android")'.dependencies.android_glue]
|
2016-04-26 21:39:13 +10:00
|
|
|
version = "0.2"
|
2015-01-01 09:10:29 +11:00
|
|
|
|
2016-05-03 07:58:52 +10:00
|
|
|
[target.'cfg(target_os = "ios")'.dependencies]
|
2016-03-21 10:04:11 +11:00
|
|
|
objc = "0.2"
|
2015-09-22 02:57:35 +10:00
|
|
|
|
2016-05-03 07:58:52 +10:00
|
|
|
[target.'cfg(target_os = "macos")'.dependencies]
|
2016-03-21 10:04:11 +11:00
|
|
|
objc = "0.2"
|
2018-02-06 00:34:37 +11:00
|
|
|
cocoa = "0.14"
|
|
|
|
|
core-foundation = "0.5"
|
|
|
|
|
core-graphics = "0.13"
|
2015-01-10 20:56:47 +11:00
|
|
|
|
2017-12-25 00:46:47 +11:00
|
|
|
[target.'cfg(target_os = "windows")'.dependencies.winapi]
|
|
|
|
|
version = "0.3"
|
|
|
|
|
features = [
|
|
|
|
|
"winnt",
|
|
|
|
|
"winuser",
|
|
|
|
|
"wingdi",
|
|
|
|
|
"shellapi",
|
|
|
|
|
"dwmapi",
|
|
|
|
|
"processthreadsapi",
|
|
|
|
|
"libloaderapi",
|
|
|
|
|
"windowsx",
|
|
|
|
|
"hidusage",
|
2018-04-13 03:12:15 +10:00
|
|
|
"combaseapi",
|
|
|
|
|
"objbase",
|
|
|
|
|
"unknwnbase",
|
2017-12-25 00:46:47 +11:00
|
|
|
]
|
2015-08-22 01:49:10 +10:00
|
|
|
|
2016-07-31 06:08:00 +10:00
|
|
|
[target.'cfg(any(target_os = "linux", target_os = "dragonfly", target_os = "freebsd", target_os = "openbsd"))'.dependencies]
|
2018-05-06 03:36:34 +10:00
|
|
|
wayland-client = { version = "0.20.2", features = [ "dlopen", "egl", "cursor"] }
|
|
|
|
|
smithay-client-toolkit = "0.2.1"
|
2018-04-27 01:53:11 +10:00
|
|
|
x11-dl = "2.17.5"
|
X11: General cleanup (#491)
* X11: General cleanup
This is almost entirely internal changes, and as usual, doesn't actually
fix any problems people have complained about.
- `XSetInputFocus` can't be called before the window is visible. This
was previously handled by looping (with a sleep) and querying for the
window's state until it was visible. Now we use `XIfEvent`, which blocks
until we receive `VisibilityNotify`. Note that this can't be replaced
with an `XSync` (I tried).
- We now call `XSync` at the end of window creation and check for
errors, assuring that broken windows are never returned. When creating
invisible windows, this is the only time the output buffer is flushed
during the entire window creation process (AFAIK). For visible windows,
`XIfEvent` will generally flush, but window creation has overall been
reduced to the minimum number of flushes.
- `check_errors().expect()` has been a common pattern throughout the
backend, but it seems that people (myself included) didn't make a
distinction between using it after synchronous requests and asynchronous
requests. Now we only use it after async requests if we flush first,
though this still isn't correct (since the request likely hasn't been
processed yet). The only real solution (besides forcing a sync *every
time*) is to handle asynchronous errors *asynchronously*. For future
work, I plan on adding logging, though I don't plan on actually
*handling* those errors; that's more of something to hope for in the
hypothetical async/await XCB paradise.
- We now flush whenever it makes sense to. `util::Flusher` was added to
force contributors to be aware of the output buffer.
- `Window::get_position`, `Window::get_inner_position`,
`Window::get_inner_size`, and `Window::get_outer_size` previously all
required *several* round-trips. On my machine, it took an average of
around 80µs. They've now been reduced to one round-trip each, which
reduces my measurement to 16µs. This was accomplished simply by caching
the frame extents, which are expensive to calculate (due to various
queries and heuristics), but change infrequently and predictably. I
still recommend that application developers use these methods sparingly
and generally prefer storing the values from `Resized`/`Moved`, as
that's zero overhead.
- The above change enabled me to change the `Moved` event to supply
window positions, rather than client area positions. Additionally, we no
longer generate `Moved` for real (as in, not synthetic)
`ConfigureNotify` events. Real `ConfigureNotify` events contain
positions relative to the parent window, which are typically constant
and useless. Since that position would be completely different from the
root-relative positions supplied by synthetic `ConfigureNotify` events
(which are the vast majority of them), that meant real `ConfigureNotify`
events would *always* be detected as the position having changed, so the
resultant `Moved` was multiple levels of misleading. In practice, this
meant a garbage `Moved` would be sent every time the window was resized;
now a resize has to actually change the window's position to be
accompanied by `Moved`.
- Every time we processed an `XI_Enter` event, we would leak 4 bytes via
`util::query_pointer` (`XIQueryPointer`). `XIButtonState` contains a
dynamically-allocated mask field which we weren't freeing. As this event
occurs with fairly high frequency, long-running applications could
easily accumulate substantial leaks. `util::PointerState::drop` now
takes care of this.
- The `util` module has been split up into several sub-modules, as it
was getting rather lengthy. This accounts for a significant part of this
diff, unfortunately.
- Atoms are now cached. Xlib caches them too, so `XInternAtom` wouldn't
typically be a round-trip anyway, but the added complexity is
negligible.
- Switched from `std::sync::Mutex` to `parking_lot::Mutex` (within this
backend). There appears to be no downside to this, but if anyone finds
one, this would be easy to revert.
- The WM name and supported hints are now global to the application, and
are updated upon `ReparentNotify`, which should detect when the WM was
replaced (assuming a reparenting WM was involved, that is). Previously,
these values were per-window and would never update, meaning replacing
the WM could potentially lead to (admittedly very minor) problems.
- The result of `Window2::create_empty_cursor` will now only be used if
it actually succeeds.
- `Window2::load_cursor` no longer re-allocates the cursor name.
- `util::lookup_utf8` previously allocated a 16-byte buffer on the heap.
Now it allocates a 1024-byte buffer on the stack, and falls back to
dynamic allocation if the buffer is too small. This base buffer size is
admittedly gratuitous, but less so if you're using IME.
- `with_c_str` was finally removed.
- Added `util::Format` enum to help prevent goofs when dealing with
format arguments.
- `util::get_property`, something I added way back in my first winit PR,
only calculated offsets correctly for `util::Format::Char`. This was
concealed by the accomodating buffer size, as it would be very rare for
the offset to be needed; however, testing with a buffer size of 1,
`util::Format::Long` would read from the same offset multiple times, and
`util::Format::Short` would miss data. This function now works correctly
for all formats, relying on the simple fact that the offset increases by
the buffer size on each iteration. We also account for the extra byte
that `XGetWindowProperty` allocates at the end of the buffer, and copy
data from the buffer instead of moving it and taking ownership of the
pointer.
- Drag and drop now reliably works in release mode. This is presumably
related to the `util::get_property` changes.
- `util::change_property` now exists, which should make it easier to add
features in the future.
- The `EventsLoop` device map is no longer in a mutex.
- `XConnection` now implements `Debug`.
- Valgrind no longer complains about anything related to winit (with
either the system allocator or jemalloc, though "not having valgrind
complain about jemalloc" isn't something to strive for).
* X11: Add better diagnostics when initialization fails
* X11: Handle XIQueryDevice failure
* X11: Use correct types in error handler
2018-05-03 23:15:49 +10:00
|
|
|
parking_lot = "0.5"
|
2017-12-13 22:22:03 +11:00
|
|
|
percent-encoding = "1.0"
|
