Input and Display status update
Tue Oct 24 13:12:00 GMT 2000
Thanks for your input and interest in the project,
From: firstname.lastname@example.org [ mailto:email@example.com ]
Sent: Tuesday, October 24, 2000 11:16 AM
Subject: RE: Input and Display status update
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.
[ mailto:Harold@compasstechnologies.com ]
Sent: Monday, October 23, 2000 2:06 AM
Subject: Input and Display status update
Today I finished my first round of key mappings for the Windows virtual
codes to the codes that X uses. These new key mappings are needed to
replace the DirectInput keyboard code with standard keyboard input
have built and tested the key mappings, and I've got everything working
a US keyboard) except the NumLock key.
The display code hasn't moved much; I'm still at the point where I
the overlay for the X window screen within a Windows window, but I have
do a little more math on positioning the window so that video card
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
test release on Win9X, as I haven't really seen anyone reporting
with DirectInput acquiring the mouse (though lots of people have had
problems acquiring the keyboard).
More information about the Cygwin-xfree