[Pyobjc-dev] [ pyobjc-Bugs-2982093 ] Mouse event locations broken for 64 bit
Brought to you by:
ronaldoussoren
From: SourceForge.net <no...@so...> - 2010-04-05 14:04:27
|
Bugs item #2982093, was opened at 2010-04-05 16:04 Message generated for change (Tracker Item Submitted) made by You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=114534&aid=2982093&group_id=14534 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Pepijn de Vos () Assigned to: Nobody/Anonymous (nobody) Summary: Mouse event locations broken for 64 bit Initial Comment: When PyObjC is ran in 64 bit mode(which is the default) on Snow Leopard creating a mouse event returns a garbage location. When I run this code, everything goes back to normal: defaults write com.apple.versioner.python Prefer-32-Bit -bool yes This is an example code, note the returned NSPoint. >>> from Quartz import * >>> event = CGEventCreateMouseEvent(None, kCGEventLeftMouseDown, (200, 200), 0) >>> CGEventGetLocation(event) <NSPoint x=13510801139695616.0 y=6.953222975628442e-310> Events captured from an event tap instead of generated do have a correct position, as do separate NSPoint objects. The problem is really with creating an event in 64 bit Python. I'm using Python 2.6 and PyObjC 2.2 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=114534&aid=2982093&group_id=14534 |