Re: Re: Mac fkeys
Re: Re: Mac fkeys
- Subject: Re: Re: Mac fkeys
- From: "Mark Munz" <email@hidden>
- Date: Thu, 26 Oct 2006 09:55:10 -0700
But that's an Application-specific issue. I'm referring to system-wide
hot keys, when installed, prevent your app from ever getting the keys
in the first place.
Case in point, if you were to write an emulator. Say you wanted to
emulate an Apple II machine. Well, all the hot keys prevent you from
even seeing the keys in your program (and I haven't found a way to
truly disable this), or worse, the system acts on it AND you get the
keystroke. So if you press Cmd-Shift-Q, you're prompted to shutdown.
I do think the Application should have control over this. Whether it
is an Apple II emulator or a Help Desk system, if your designing a
specialty app -- you should be able to meet the specs required w/o
Apple getting in the way.
And yes, I've tried SetSystemUIMode, but it doesn't seem to work well
as far as I can tell.
On 10/26/06, Jeffrey Oleander <email@hidden> wrote:
> One suggestion might be to add a "User" modifier key.
> Apple should then have a policy not to use the "User"
> modifier. This would give the user at least the option
> of User-F1 or User-Opt-F1, etc.
Or, on my ancient Pismo, user+fn+f1 or user+opt+fn+f1, etc.
I'll second that.
OTOH, in some cases Apple hasn't "gone key-equivalent mad"
enough. Some of the buttons on the Apple-supplied services
need key equivalents. Just this moment I'm thinking of the
find/replace dialog box.
--
Mark Munz
unmarked software
http://www.unmarked.com/
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden