Index: [thread] [date] [subject] [author]
  From: Rodolphe Ortalo <Rodolphe.Ortalo@cert.fr>
  To  : ggi-develop@eskimo.com
  Date: Wed, 26 May 1999 12:02:46 +0200

Re: Debugging, GII_INPUT and OpenAmulet-on-LibGWT

Marcus Sundberg wrote:
> Do a cvs update and recompile LibGWT. ;-)

Ahemm... LibGwhat ? :-)))

> > Did I make a BIG mistake in the GII_INPUT env. variable configuration ?
> 
> No, the mistake was in gwtCreateRootWindow() which looked really
> weird to me. ;)
> I'm not sure exactly what you were trying to achieve with that code,
> or if you just got the idea of LibGII/LibGGI wrong? Please have a look
> at my new gwtCreateRootWindow() and the updated demos, and tell me
> if that does what you wanted.

Well. Surely. I have to admit that I am a little confused
on the GGI<->GII interaction...
E.g.: with did you use 'ggiJoinInputs' in gwtCreateRootWindow
and not some form of   'giiJoinInputs' ?

Well, so, it seems a ggi_visual_t comes with its own gii_input_t
ready? Can you access that one with gii* functions or do you
always need to rely on the existence of a ggi* equivalent ?
(This is for consistence among the way GWT obtain events on
{root,child,offscreen} windows.)

I was suspecting that in fact... But I think I'd better use
GII functions directly for everything as, for 'normal' (non-root)
windows, I use a 'input-null' GII input to queue the events...
(These windows have no associated ggi_visual_t.) Am I right
to say so or are there other implications ?

BTW: You are right, if I can access the gii_input_t furnished
with a ggi_visual_t, the 'inp' parameter of gwtCreateRooWindow
is not useful at all...

Rodolphe

Index: [thread] [date] [subject] [author]