Index: [thread] [date] [subject] [author]
  From: becka@rz.uni-duesseldorf.de
  To  : ggi-develop@eskimo.com
  Date: Mon, 10 May 1999 16:38:15 +0200 (MET DST)

Re: Troubles with ggiSetEvent

Hi !

> This is completed with then following code :
> 	ggiEventRead(vis,&MyEv,emKeyPress);
> Then I wanted to do the opposite, wait for a key release then I did :
> 	ggiEventRead(vis,&MyEventKeyRelease);

> This does not work reliabily. I was using the X target.
> For times it does the expected thing, sometimes the program exited
> immediately, I had to press 4 or 5 times the keyboard.

This is strange and should be considered a bug. However I haven't seen such 
behaviour while working on LibGIC. Weird.

> Next, why should one call the ggixxxx Event function while the giixxx Event
> exists and accepts a visual.

It does not. gii* functions use a gii_input_t, which is completely different 
from 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 (could one still talk about
> visual in the gii case ?).

No. It's called an "input" in that case, but well ...

> Will it be doable to use indiferently a visual ggi instead of a visual gii
> with the exepected behaviour ?

No. There are other ways to do this, if you need to, but I'll explain that
in another reply to this thread.

CU, Andy

-- 
Andreas Beck              |  Email :  <Andreas.Beck@ggi-project.org>

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