TGE conflict w/ Expose
by Matthew "Scandalon" Parsons · in Torque Game Engine · 08/08/2003 (2:46 pm) · 9 replies
Function key calls (F11 for editor, F10 for Screenshot, IIRC) are intercepted by expose (10.3 feature for window/app management/navigation), so, instead of pulling up the mission editor, it'll slide all windows out of the way, for example. I'll have to go back and check to see if a user can disable Expose, and I expect it won't be too difficult to overide in the normal TGE startup (or better yet, whenever it's active) but it's something to be aware of.
#2
08/08/2003 (3:40 pm)
True. (And I almost mentioned that in the original post.) But it's still an issue (albeit minor) that should be fixed for the core engine. 1. Those function keys are now useless. 2. You don't want platform-specific interface changes. 
#3
It does in Jaguar, that's how I use my Function keys when I run tge on my ibook.
Do you know the trick I mean ? Or do you have a mac that can't truly boot in 9 ?
08/08/2003 (4:17 pm)
In Panther, does booting in MacOS 9 and toggling the function keys thingy still work ?It does in Jaguar, that's how I use my Function keys when I run tge on my ibook.
Do you know the trick I mean ? Or do you have a mac that can't truly boot in 9 ?
#4
08/08/2003 (9:15 pm)
Nicolas, I have no idea what you mean. Sorry.
#5
Is that clearer ?
08/09/2003 (9:43 am)
Okay, you boot into 9. Go to the control panels, one of them, don't remember which one off hand (and I'm in Jaguar right now ;)) has a Function Keys option : with that checkbox you can invalidate the hard wired fkeys option that Apple makes default, especially on portables (F1 dims screen, etc.). The settings are stored in nvram, so when you reboot in OS X, the options are still set, and your function keys are free to be mapped to whatever use you want. If you use the fn key with the f keys, you get the old default behavior. Is that clearer ?
#6
08/10/2003 (9:02 pm)
Much clearer. I doubt the new setting are in NVRAM, but I can try it.
#7
And it has to be store in nvram has the pref survives cold reboots into MacOS X.
Have you tried apple's mailing lists or forums to address the issue : the more people scream about the "hard wired" function keys in OS X, the more chances we have of getting the same level of functionality that was present in the older OSes.
Note : you have to boot into 9, not start Classic for this to work, as it needs "native" hardware access to work, which Classic doesn't have
08/11/2003 (9:34 am)
Well, all it does afaik, is change the need for using the fn key to be able to use the function keys for something else than the default settings : ie, it's a toggle. And it has to be store in nvram has the pref survives cold reboots into MacOS X.
Have you tried apple's mailing lists or forums to address the issue : the more people scream about the "hard wired" function keys in OS X, the more chances we have of getting the same level of functionality that was present in the older OSes.
Note : you have to boot into 9, not start Classic for this to work, as it needs "native" hardware access to work, which Classic doesn't have
#8
Well, that should take care of Mathew's problem
08/12/2003 (12:05 pm)
Oh, I thought such functionality wasn't available : I don't have the Panther seed available to me, so I can't test it :)Well, that should take care of Mathew's problem
#9
08/12/2003 (12:13 pm)
Please see my third post. (It's not a problem for *me*, but it is for the engine.) 
Torque Owner Harold "LabRat" Brown
F11: Mission Editor: example/common/editor/editor.cs
Last line
F10: GuiEditor: example/common/ui/GuiEditorGui.gui
Last Line