This is the mail archive of the
cygwin-xfree@cygwin.com
mailing list for the Cygwin XFree86 project.
RE: Possibly incorrect explanation of how WaitForSomething works (and how to fix it) [RC and CGF please comment]
- To: <cygwin-xfree at cygwin dot com>
- Subject: RE: Possibly incorrect explanation of how WaitForSomething works (and how to fix it) [RC and CGF please comment]
- From: "Robert Collins" <robert dot collins at itdomain dot com dot au>
- Date: Wed, 11 Apr 2001 09:23:19 +1000
- Thread-Index: AcDCE3bOvVpe087lR3a5C1GYloxniwAAVq1Q
- Thread-Topic: Possibly incorrect explanation of how WaitForSomething works (and how to fix it) [RC and CGF please comment]
> -----Original Message-----
> From: Christopher Faylor [mailto:cgf@redhat.com]
> Sent: Wednesday, April 11, 2001 6:09 AM
> To: Cygx (E-mail)
> Subject: Re: Possibly incorrect explanation of how WaitForSomething
> works (and how to fix it) [RC and CGF please comment]
>
>
> On Tue, Apr 10, 2001 at 08:09:48AM +1000, Robert Collins wrote:
> >I thought cygwin had fd support for keyboard and mouse? If
> it doesn't,
> >then my suggestion would be: write it.
>
> It only supports the keyboard and the mouse in the context of
> the console.
> I don't think that is appropriate for the X server.
>
> cgf
>
I'm just curious here: In Unix as I understand it, the X server physical
screen gets a pty? for access to the keyboard, and opens /dev/mouse |
/dev/cua0 | ...
What makes those things inappropriate for cygwin support? I'd have
thought that a win32 message queue handler in a cygwin linked app would
be more trouble than cygwin handling the messages...
Rob