(no subject)

[Amavect .]

All,

I'm trying to write a gui program with using both keyboard(2) and stdin.
It appears that there's a race between /dev/cons and stdin.
Shouldn't only keyboard(2) get the character?
Example: http://okturing.com/src/7981/body


#include <u.h>
#include <libc.h>
#include <draw.h>
#include <cursor.h>
#include <thread.h>
#include <keyboard.h>
#include <mouse.h>

void
stdinproc(void *aux)
{
Channel *c;
char in;
long n;

c = aux;

for(;;){
n = read(0, &in, sizeof(in));
if(n != 0){
send(c, &in);
}else{
print("stdin: closed?");
threadexitsall(nil);
}
}
}

void
threadmain(int, char **)
{
Keyboardctl *kctl;
Rune r;
char inc;
Channel *stdinc;

stdinc = chancreate(sizeof(char), 8);
proccreate(stdinproc, stdinc, 0x2000);

if((kctl = initkeyboard(nil)) == nil)
sysfatal("%r");

enum { KEYS, STDIN, NONE };
Alt alts[] = {
[KEYS]   = {kctl->c, &r, CHANRCV},
[STDIN]  = {stdinc, &inc, CHANRCV},
[NONE]   = {nil, nil, CHANEND}
};

for(;;){
switch(alt(alts)){
case KEYS:
if(r == Kdel)
threadexitsall(nil);
print("keys: %C\n", r);
break;
case STDIN:
print("stdin: %c\n", inc);
break;
case NONE:
print("NOPE\n");
break;
}
}
}

Re:

[Anthony Martin]

"Amavect ." <amavect@gmail.com> once said:
> I'm trying to write a gui program with using both keyboard(2) and stdin.
> It appears that there's a race between /dev/cons and stdin.
> Shouldn't only keyboard(2) get the character?
> Example: http://okturing.com/src/7981/body

What output do you expect when standard input is /dev/cons?
Both the internal keyboard(2) process and your stdinproc are
reading from the same underlying file.

Try redirecting the standard input of your program from another
file and and report back the results.

Cheers,
  Anthony

Re: [9front] Re:

[Amavect .]

Ah, it's still reading /dev/cons through stdin.
I've been pointed to reading /dev/kbd directly.
Thanks for the help.

Thanks,
Amavect

On Fri, Mar 13, 2020 at 2:53 AM Anthony Martin <ality@pbrane.org> wrote:
>
> "Amavect ." <amavect@gmail.com> once said:
> > I'm trying to write a gui program with using both keyboard(2) and stdin.
> > It appears that there's a race between /dev/cons and stdin.
> > Shouldn't only keyboard(2) get the character?
> > Example: http://okturing.com/src/7981/body
>
> What output do you expect when standard input is /dev/cons?
> Both the internal keyboard(2) process and your stdinproc are
> reading from the same underlying file.
>
> Try redirecting the standard input of your program from another
> file and and report back the results.
>
> Cheers,
>   Anthony