Index: [thread] [date] [subject] [author]
  From: BERNARD Sebastien <sebastien.bernard@cegetel.fr>
  To  : 'ggi-develop@eskimo.com' <ggi-develop@eskimo.com>
  Date: Mon, 10 May 1999 15:23:59 +0200

RE: Troubles with ggiSetEvent

Well, I felt a bit confused.
One side, you have a set of giixxx Verbs which wants some gii_input_t
context.
In application, you're dealing with some ggi_visual_t.
How are you doing the link between both ? (I found it by myself).

I was a little tired when I tried yesterday. So I gave the giiEventRead a
visual.
The result was a core dump of course.

I don't know why their is such a double declaration like :
	giixxxEvent  <---> ggixxxEvent
It is double work to stay up to date with gii library API.

Shall we have simply a function like :
	gii_input_t ggiGetInput(ggi_visual_t);
and tell the developper if he wants to get some input, he has to call that
function to get the
handle, then use it with the giixxx verbs (something like : please refer to
man page for gii library for more information).


> -----Message d'origine-----
> De:	Andrew Apted [SMTP:ajapted@netspace.net.au]
> Date:	lundi 10 mai 1999 15:03
> À:	ggi-develop@eskimo.com
> Objet:	Re: Troubles with ggiSetEvent
> 
> BERNARD Sebastien writes:
> 
> >  Next, why should one call the ggixxxx Event function while the giixxx
> Event
> >  exists and accepts a visual.
> 
> LibGII functions accept a gii_input_t, but not a ggi_visual_t.
> 
> >  Instead or using giiEventRead, one has to use ggiEventRead which has
> the
> >  only purpose to call giiEventRead with the same parameters and the
> >  visual set to vis-input
> 
> Yep, LibGGI is a client of LibGII.  What's the problem ?
> 
> Cheers,
> ___________________________________________________
>                                                \  /
>   Andrew Apted   <ajapted@netspace.net.au>      \/
>  

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