This is the mail archive of the
cygwin-xfree@sources.redhat.com
mailing list for the Cygwin project.
RE: Input and Display status update
- TO: cygwin-xfree at sources dot redhat dot com
- Subject: RE: Input and Display status update
- From: j dot j dot ita at siep dot shell dot com
- Date: Tue, 24 Oct 2000 17:16:29 +0200
Harold,
I vote for finishing off the display code before dealing with the
mouse. As we have seen from the list, some people have DirectX problems
(on Windows NT) that the "-screen 0" solution does not fix. I am one of
them. I would be interested to see if the code you have implemented
provides a workaround to this. If you need a tester, you have your man.
Joel Ita
j.j.ita@siep.shell.com
-----Original Message-----
From: Harold@compasstechnologies.com
[mailto:Harold@compasstechnologies.com]
Sent: Monday, October 23, 2000 2:06 AM
To: cygwin-xfree@sources.redhat.com
Subject: Input and Display status update
Today I finished my first round of key mappings for the Windows virtual
key
codes to the codes that X uses. These new key mappings are needed to
replace the DirectInput keyboard code with standard keyboard input
code. I
have built and tested the key mappings, and I've got everything working
(on
a US keyboard) except the NumLock key.
The display code hasn't moved much; I'm still at the point where I
display
the overlay for the X window screen within a Windows window, but I have
to
do a little more math on positioning the window so that video card
alignment
and size restrictions for overlays are met.
I have not started on replacing the DirectInput mouse code with standard
mouse input functions. I'm not sure if this would be worth it for an
intial
test release on Win9X, as I haven't really seen anyone reporting
problems
with DirectInput acquiring the mouse (though lots of people have had
problems acquiring the keyboard).
Harold