Dustin Bensing
Dustin Bensing
It would be very helpful to get more examples that show the features and possibilities of this library. It would help tremendously to set boundaries of what to expect for...
- what do i need from Wayland side - is this even possible with the Wayland security measures?
Try to enable MIRI – take a look here https://www.reddit.com/r/rust/comments/e1az07/fyi_if_you_have_a_crate_that_involves_a_lot_of/
Implements the Extension trait for Linux, macOS and Windows to get the display dimensions and the mouse position see https://github.com/enigo-rs/enigo/issues/74 - [x] Linux impl - [x] macOS impl - [x]...
We already have implementations for [win](https://github.com/enigo-rs/enigo/blob/949da7042904921530d27a19ebcb2e7bb3615839/src/win/win_impl.rs#L159) and [mac](https://github.com/enigo-rs/enigo/blob/949da7042904921530d27a19ebcb2e7bb3615839/src/macos/macos_impl.rs#L410) so we just need one for Linux and are good to go and can implement it on the "general" [Enigo struct](https://github.com/enigo-rs/enigo/blob/949da7042904921530d27a19ebcb2e7bb3615839/src/lib.rs#L380) or...
The DSL has a limited amount of buttons that it currently supports. In the first iteration i think its a good idea to support all layout independent ones.
investigate how to bound check the mouse cursor (is this necessary? does that cause errors/panics?)
use interior mutability to alter internal fields. It is un-ergonomic to bind Enigo mutably.
Only unsigned integer possible to move on `rasterspace`
- What do i need from Redox side to integrate enigo? - talk about that with jackpot51