LSUIElement and hot keys
LSUIElement and hot keys
- Subject: LSUIElement and hot keys
- From: Chase <email@hidden>
- Date: Mon, 18 Jul 2005 07:27:31 -0500
Okay, I have a new issue with LSUIElement that needs resolving.
If I have (just as an example) TextEdit.app open and the user clicks
on my status item in the menu bar, which opens a window in my app...
my app is the "active" app at that point.
This is a good thing for a thousand other reasons, but there's just
one problem... key commands, like (just an example) command+Q, are
intercepted and processed in my app instead of TextEdit, even though
the user sees the TextEdit menu bar at the top of the screen.
Should I pass those keystrokes to the appropriate app, or ignore
them. My app should not be quit in this manner, that's for sure.
Can I allow them to pass thru me to the next app?
To me, I would think this would irritate me as a user, to see the
TextEdit menu bar and yet my key commands either do nothing or seem
to affect this other utility app that doesn't have a main menu bar.
It's weird to me, but I'll admit, it may still be appropriate to
**not** send keyboard shortcuts to TextEdit (or whatever) while my
LSUIElement's window is open and "active".
At the bare minimum, I could to cut off Quit/Copy/Paste/etc... in my
app, because I don't use any of those shortcuts. My app can
certainly be quit, but it's initiated in another way.
What should I do?
- Chase
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden