Andreas Beck wrote:
> > keep in mind that our synthesized ggi events aren't correctly initialized.
> > Half of the information is missing. We have to look into the gii docs and
> > reconstruct the missing part, or else rethink our key event structure, if
> > it turns out to be essential.
>
> Hmm - I got to recheck. I am pretty sure it worked on cube3d. Anything
> special you do ?
I'll play with ggi-in-berlin myself a bit more to get a better understanding.
There is another question, related to key events. GGI key events contain a number
of members, notably 'sym', 'label', and 'button'. In what way are these three members
independent ? I understand that you may use a different 'mapping' (as in X), so
a sym doesn't correspond necessarily always to the same key. However, given that
the mapping is done at a lower level, isn't the goal to shield the application
(GGI in this case) from the button ? Shouldn't it then only care about the *meaning*,
instead of the physical key being pressed ?
And what about the label ? Is that pure convenience ?
I'm asking as I didn't make up my mind about how to represent key events in berlin.
We currently have a 'Toggle', which contains the (unicode) value of the key being
pressed. Another member of the event, a 'telltale' may contain flags representing
'modifiers'.,
(the idea of berlin events is to totally abstract from physical devices, such as
keyboard,
mouse, etc. In order to be flexible towards new devices as well as 'device emulation',
I
prefer to synthesize events out of basic building blocks (toggles, telltales,
positions,
values, etc.) and then specify in a config tool what they mean and how physical (ggi)
events
map to them...
Regards, Stefan
_______________________________________________________
Stefan Seefeld
Departement de Physique
Universite de Montreal
email: [EMAIL PROTECTED]
_______________________________________________________
...ich hab' noch einen Koffer in Berlin...
