Suggestion: replace SetCursorPos() by mouse_event()

[falcondai]

in windows implementation, instead of windll.user32.SetCursorPos(x, y), use mouse_event with MOUSEEVENTF_MOVE provides better integration in my experience.

[pepijndevos]

Go for it, if you want.

I don't use windows, I'm on vacation, and I'm not really maintaining pymouse anymore.

Sent from my iPod

On 31 mei 2012, at 15:04, Falcon Daireply@reply.github.com wrote:

in windows implementation, instead of windll.user32.SetCursorPos(x, y), use mouse_event with MOUSEEVENTF_MOVE provides better integration in my experience.

---

Reply to this email directly or view it on GitHub:
#13

[falcondai]

lol. cool. (i imagine this comment might help future developers who use
pymouse)

On Thu, May 31, 2012 at 2:44 PM, Pepijn de Vos <
reply@reply.github.com

wrote:

Go for it, if you want.

I don't use windows, I'm on vacation, and I'm not really maintaining
pymouse anymore.

Sent from my iPod

On 31 mei 2012, at 15:04, Falcon Daireply@reply.github.com wrote:

in windows implementation, instead of windll.user32.SetCursorPos(x, y),
use mouse_event with MOUSEEVENTF_MOVE provides better integration in my
experience.

---

Reply to this email directly or view it on GitHub:
#13

---

Reply to this email directly or view it on GitHub:
#13 (comment)

Falcon Dai