"Brian S. Julin" wrote:
> On Sun, 21 May 2000, Jay wrote:
>
> > Marcus Sundberg wrote:
> >
> > > If you are calling any gii* functions you are likely (but not
> > > necessarily) doing something wrong. I need to look at the full
> > > code to know for certain though.
>
> > Really? Then how am I supposed to get input?
>
> With the ggi* functions. Unless you are not using a visual there's
> rarely a reason to use gii* functions when the equivalent ggi* functions
> are available.
>
> (P.S. Stay tuned, I'm working on a libGII-only app that essentially adds
> FN key macros, scripts, and pseudo command-history on a host-by-host basis for
> people needing to telnet around to network gear and such, being as I
> need one at work. Sort of like a com program, but without the full-screen
> terminal emulator or rs232 baggage, and far more customizable.)
>
> --
> Brian
Well, then what I'm doing is extreemly wrong. But if I do it any other way I get
a segfault. On the console I must do this to get anything to work:
giiInit();
kbd=giiOpen("input-linux-kbd",NULL);
if (kbd==NULL) {
fprintf(stderr, "Error getting keyboard, bailing out...");
exit(1);
}
In X I must also do something simmilar, or segfault. I got my last package on the
7th of this month.
--
-Jay
