Henning Hasemann wrote:
>I dont know if this is already in discussion and I know that maybe its
>way to early for that, but its a nice idea I think, so it shouldnt get
>lost:
>
>Sometimes I get a bit angry of different applications using different
>keys for the same things.
>For example I can save a file in blender with Strg+W but in Gimp that
>closes the current window.
>Pressing the middle mouse button I can rotate the camera in blender, in
>another 3d game this works totally different again.
>And so on...
>
>So why not let there be per-user key/mouse or more general "input
>event" definitions at least for common things like saving, exiting,
> rotating the camera, and so on...
>
>
surprise, you won't need to save anything ;)
>Apllications still than could define defaults for these events to use
>them if the user didnt specify a key for it or if it runs on a system
>where no "event-mapping" is available, keeping these applications
>portable.
>
>
>Maybe this complies with that nice module-philosophy (Im referring to
> the example "I want to edit textfield in webforms with my favourite
> text editor").
>That thingy also could be written for linux, windows or any other
>system but probably wont make much sense without a certain number of
>applications using it.
>
well, i would solve it this way: global keyboard shortcuts could be
caught by a key listener component which reads and passes throught any
keys you type. this component might translate any occuring shortcuts
into specific calls you can define globally which get sent to the
corresponding component then. if the target component rejects this call
since it might not be used (eg. not supported), the keyboard (and maybe
mouse too) listener passes the the initial shortcut to the component to
let it handle by itself.
so then ...
--
Stefan Mayrhofer (Pythagoras1)
e-mail: stefan.mayrhofer@xxxxxxxxx
jabber: pythagoras1@xxxxxxxxxxx
mobile: +43 650 990 20 81
Matrikelnummer: e0526971
|
