Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Arcanor]

I have created a system to map keyboard inputs to function pointers in my application.

I'm noticing that there are certain windows signals and other behaviors that are generated when using certain key combinations, for example:

- alt-f4: terminates the application
- alt-space: opens the top left (titlebar) window menu
- alt-(any character): causes a beep sound, but it still processes my application's command map

The question is: how do people normally deal with these?  I guess I could avoid mapping alt-key combinations entirely but I'd like to be able to use them if possible.  And maybe there are other keys with Control- modifiers that should be avoided too?

Is there a convenient list of specific key combinations that I should NOT be allowing to be mapped in my application?  Alt-f4 is an obvious one, and alt-space too, but are there others?

Also, how can I keep windows from beeping every time I hit alt-1, alt-a, alt-q, etc.?

[pjcast]

Alt tab is another one. There are various window's hooks you can use to disable the default functionality - however, it is strongly discouraged to mess with system key shortcuts.

As for alt beeping, make sure you have the latest Eihort, it should cleanly handle the Alt key getting stolen from the system menu.

[Arcanor]

I do have the latest Eihort.  Just downloaded a couple days ago from cvs in the "v1-4" branch.  Alt keys are still beeping.  Do I need to do something special to keep it from happening?

[pjcast]

Wierd, I surely don't see alt keys beeping here.

[Arcanor]

Alt-keys are definitely still beeping for me, even on the Ogre demos right out of the box after building the new final release.  For example, the BSPCollision or Ocean demo.  I hit alt-F and it beeps but still processes the 'f' to hide the gui.

Since the ogre demos use ois, this should be confirmable by others who run them.

I have just posted this question to the ogre forum.  We'll see if anyone there has had a similar experience.

[Arcanor]

Just to follow up, this required a patch being submitted to the Ogre engine.  pjcast - I still have no idea why you weren't seeing the problem.

In any case, this problem will be solved once the Ogre patch is accepted and applied.