> > I found the bug in GGI::Visual that was preventing events from being
> > forwarded; had to fill in the event.any.target field, or it was discarded
> > by ggiEventSend.
> strange. Why is this needed ? Events are sent to visuals.
No. Events are sent to the GII subsystem. You need to set event->any.target
to GII_EV_TARGET_QUEUE if you want to queue what you send.
The events can as well be used to control the input subsystems by sending to
GII_EV_TARGET_ALL or a origin number.
> So what is the target good for ?
Controlling inputs. Say making force-feedback possible or configuring
stuff on the fly.
> The SendEvent already takes the visual as argument. It seems redundant
> somehow...
See above.
> > Unfortunately, this still isn't enough to make everything
> > work perfectly; applications that poll for any key (say, the dots demo)
> > work correctly. Applications that pause and wait (eg, the standard
> > demo) do not -- there seems to be a failure in giiEventPoll for the SHM
> > target.
> 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 ?
CU, ANdy
--
= Andreas Beck | Email : <[EMAIL PROTECTED]> =
