--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google Groups "Chromium-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-dev+unsubscribe@chromium.org.
// We use the deprecated CGPostMouseEvent API because we receive low-level // mouse events, whereas CGEventCreateMouseEvent is for injecting higher-level // events. For example, the deprecated APIs will detect double-clicks or drags // in a way that is consistent with how they would be generated using a local // mouse, whereas the new APIs expect us to inject these higher-level events // directly.
I also found that using CGPostMouseEvent is the only way to get mouse events simulatedon login window. The non deprecated API way of doing this using CGEventCreateMouseEvent + CGEventPost doesn't work in login window. Any idea on how this will be handled when the deprecated API is removed?