xenic wrote:I use a lot of seperate screens and after I've iconified a program from a seperate screen to reduce screen crowding, I find it convenient to be able to reopen the iconified program with a hotkey rather than switching to the Workbench screen, clicking the icon and then returning to the screen I'm working on.
That's fair enough, however I'd argue this is exactly what the FKey commodity is for. It ideally needs to be expanded to contain some commands for "send application.library SHOW command to...", then there is no excuse for applications implementing their own global popup keys. However in the current incarnation you can put an ARexx command in to bring the application to the front.
This
really needs to go into the style guide or something to stop it happening (or at least to make it easier to argue about!). "Do not install a global input handler without a very good reason". "Applications do not need global popup keys unless they are designed to be run hidden (ie. they are commodities)". "A web browser or email client is not a commodity!"
On the other hand, I can see how Commodities hotkey use can be abusive. I still use Turbotext which allows unlimited global hotkeys to be defined. I recently discovered why some hotkeys are unavailabe for "REAL" commodity use. Turbotext defines 5 global hotkeys in the default preferences. Ugh, bad idea; I need to get rid of those.
If those are hotkeys just for Turbotext, they should not be global. It should only be listening for keyboard commands when the window is active. If they are really global and there's no need for it, that is certainly bad practice. Too late to do anything about it now, but it brings me back to my style guide point.