How can I get current location of cursor?

it can move at the normal window, but only cannot move in osu.
when my mouse in osu window, I can move it free.

I know that this crate doesn't have any animation logic, however I'd like to find a way to use this lib (move mouse cursor) with animation. Is there any crates to do this?

I was going mad at how the pointer location was inaccurate before I figured this out: windows scaling options also scales the mouse location when using move_to().

Despite my monitor being 1920x1080, move_to() is also scaled by 125%, meaning I reach the bottom right corner of the screen at move_to(1536, 864)

I realize this project hasn't been updated in a year but this is probably unintentional and I hope someone can get around to fixing it.

Worth noting it's not a huge deal if you know the current scale, but the problem is if I'm giving the program to someone else.

let mouse = Mouse::new();
let loc_x = (f64::from(INTENDED_X) / 1.25).floor() as i32; // Assuming you're at 125% scale. 
let loc_y = (f64::from(INTENDED_Y) / 1.25).floor() as i32; // Not 100% accurate because it has to be i32, so I have to floor or get average.
mouse.move_to(loc_x, loc_y);

This function would move mouse by x, y. Instead of moving mouse absolute it would move relative.

first of all, great package, fits my use case perfectly.
it'd be awesome to be able to lock the mouse in a box (not sure if this would be outside the scope of this crate).
Say for example I have coordinates, width and height.
I want to lock the mouse in that rectangle.
For example calling a function like fn lock_mouse(x: i32, y: i32, width: i32, height: i32) would lock the mouse in that rectangle.
kind of an equivalent to winit's set_cursor_grab (see here)
and, of course, a function to unlock it as well.

Hello, this library looks pretty good. Mouse::get_position returns the mouse's global position anywhere on the screen. How about having a method for getting the mouse's position relative to the window?

Really appreciate the work done on this library, thank you :)

Issue

The Mouse::move_to method under sys::macos does not fire an event when the mouse is moved. From Apple docs, CGDisplayMoveCursorToPoint does not generate events. The result is that on macOS, the cursor is moved but nothing in the UI reacts to those movements (unlike Windows, where SetCursorPos generates mouse moved messages in the Win32 message loop).

Potential Solution

Use core_graphics::event::CGEvent::new_mouse_event with the CGEventType variant MouseMoved.

Commentary

I'm not sure if this intentional or not, but it is divergent from the Windows behavior. SetCursorPos does fire events (or messages) as a part of its implementation in the Win32 API.

Additional consideration is that generating mouse moved events on macOS may prompt the user to enable the application to take control through accessibility features, which may not be clear to the library consumer or the user of the resulting application.

Edit: fixed typo

Hi,
is there a way to determine on what monitor the mouse cursor is currently at?
I would like to write a simple utility tool, that allows to move the mouse cursor between monitors easily.

Thanks in advance

Hi!
Would you be willing to relicense under MIT?

I ask because:

• Most of the rust ecosystem uses an MIT license.
• MIT provides a few additional freedoms to the end user that GPL does not (source publishing, etc)
• I'd like to use mouse-rs in a public library of my own, and I'd like to release it under an MIT license,
  but would not be able to as mouse-rs is GPL.

If not, that's fine, I thought I would ask.

Thank you!

Currently we only support X11, with the fast adoption of wayland we need to provide native support

I'm pretty new to rust and lower level programming languages in general, so this might just be missing knowledge on my side.
Is there a reason for get_position returning the coordinates as usize while move_to accepts i32?

I was just trying out some stuff and noticed I had to convert the position I'm moving to, to usize if I want to check wether the position was changed from the outside.
It's obviously not a huge issue, as long as theres a reason behind it. Otherwise I think changing it to both use the same type would improve ease of use.

Example code

use std::{thread, time};
use mouse_rs::Mouse;

fn main() {
    let mouse = Mouse::new();
    for i in 0..=1000 {
        mouse.move_to(i, i).expect("Unable to move mouse");

        thread::sleep(time::Duration::from_millis(1));

        let pos = mouse.get_position().unwrap();
        println!("{:?}", pos);

        // Convert i:i32 to i2:usize
        let i2 = i as usize;
        if pos.x != i2 || pos.y != i2 {
            break;
        }
    }
}

Edit:
I've opened a pull request for changing the Point struct to use i32 instead of usize, incase you don't like this change or have a reason why its plainly wrong please let me know :)