Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'Remove a Terminal/Illustrator keyboard conflict' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Remove a Terminal/Illustrator keyboard conflict
Authored by: derPlau on Jan 17, '05 11:43:36AM

Thanks for the link, Sapporo. The info in the link would imply that the Adobe suite uses GetKeys() for keyboard constraints. This might have something to do with the wide range of jobs the modifier keys have to do in Illustrator & Photoshop. In Illustrator, for example, if you want to select multiple objects, then move them, you hold the Shift key down to select them. But the shift key also constrains the movement, so you have to let go of the shift key if you want to move them arbitrarily. Maybe this complexity of effects requires the use of GetKeys(). Or something.



[ Reply to This | # ]
Remove a Terminal/Illustrator keyboard conflict
Authored by: arekkusu on Jan 17, '05 12:26:36PM

Ten years ago it required polling GetKeys(). Now that just wastes CPU (notice that Photoshop/Illustrator eat 100% CPU while you're dragging any tool.)

The NSEvent mechanism allows you to see the current state of modifier keys without polling, so GetKeys is definitely no longer required.



[ Reply to This | # ]