This is the mail archive of the
cygwin-xfree
mailing list for the Cygwin XFree86 project.
Re: Multimedia keys interpreted as alphabetic keys
I can confirm that the XWin you sent me does (of course) work when
-logverbose [n] is set properly, and that the old version I was using
also prints usage and exits in the same way, so it isn't and wasn't a
bug - my bad.
And now of course I can see the keycodes (or scancodes?) generated by
pressing Play/Pause twice (which used to generate a 'g' on my version),
and pressing 'g' twice for comparison.
Thanks for your help.
[2519546.968] winClipboardWindowProc - WM_WM_REINIT: Enter
[2519552.687] winWindowProc - WM_ACTIVATEAPP
[2519552.687] winClipboardWindowProc - WM_WM_REINIT: Enter
[2519552.687] winRestoreModeKeyStates: state 16
[2519552.687] winSendKeyEvent: dwKey: 70, fDown: 1, nEvents 2
[2519552.687] winSendKeyEvent: dwKey: 70, fDown: 0, nEvents 2
[2519554.109] winTranslateKey: wParam 000000b3 lParam 01000001
[2519554.109] winSendKeyEvent: dwKey: 154, fDown: 1, nEvents 2
[2519554.218] winTranslateKey: wParam 000000b3 lParam c1000001
[2519554.218] winSendKeyEvent: dwKey: 154, fDown: 0, nEvents 2
[2519555.000] winTranslateKey: wParam 000000b3 lParam 01000001
[2519555.000] winSendKeyEvent: dwKey: 154, fDown: 1, nEvents 2
[2519555.093] winTranslateKey: wParam 000000b3 lParam c1000001
[2519555.093] winSendKeyEvent: dwKey: 154, fDown: 0, nEvents 2
[2519556.859] winWindowProc - WM_ACTIVATEAPP
[2519556.859] winClipboardWindowProc - WM_WM_REINIT: Enter
[2519564.656] winWindowProc - WM_ACTIVATEAPP
[2519564.656] winClipboardWindowProc - WM_WM_REINIT: Enter
[2519564.656] winRestoreModeKeyStates: state 16
[2519564.656] winSendKeyEvent: dwKey: 70, fDown: 1, nEvents 2
[2519564.656] winSendKeyEvent: dwKey: 70, fDown: 0, nEvents 2
[2519566.265] winTranslateKey: wParam 00000047 lParam 00220001
[2519566.265] winSendKeyEvent: dwKey: 34, fDown: 1, nEvents 2
[2519566.406] winTranslateKey: wParam 00000047 lParam c0220001
[2519566.406] winSendKeyEvent: dwKey: 34, fDown: 0, nEvents 2
[2519566.921] winTranslateKey: wParam 00000047 lParam 00220001
[2519566.921] winSendKeyEvent: dwKey: 34, fDown: 1, nEvents 2
[2519567.015] winTranslateKey: wParam 00000047 lParam c0220001
[2519567.015] winSendKeyEvent: dwKey: 34, fDown: 0, nEvents 2
[2519568.046] winWindowProc - WM_ACTIVATEAPP
[2519568.046] winClipboardWindowProc - WM_WM_REINIT: Enter
On 20/04/2010 14:56, Jon TURNEY wrote:
On 20/04/2010 12:21, Chris Bird wrote:
Thanks very much for getting back to me so soon.
That seems to have fixed the problem, and I will use this version until
it's in the main build, thanks.
Thanks very much for testing the fix.
There are a couple of side effects:
1) XWin dies immediately after outputting a message on startup if I pass
it both -multiwindow and -logverbose - either in combination with other
parameters seems to be fine. I have included output into XWin.0.log in
this instance below.
A numeric verbosity level is mandatory after -logverbose, as the usage
info should make clear, so the command line below is invalid.
-logverbose verbosity
Set the verbosity of log messages. [NOTE: Only a few messages
respect the settings yet]
0 - only print fatal error.
1 - print additional configuration information.
2 - print additional runtime information [default].
3 - print debugging and tracing information.
If you can construct a command line using -logverbose without a
numeric verbosity level which is accepted, this is another bug in XWin.
2) When I ssh to another machine and start the Kate text editor, the
fonts of the menus and the file being edited are larger than usual (ie.
larger than when I use it with my old version of XWin). I restarted the
old XWin and did the same and they were back to normal size. I'm not
sure where to look for useful logging information on this.
This is expected, as the build I provided is based on the xorg-server
1.8.0-1 test release [1], which includes a change for the default DPI
value used by the X server from 75 to the value reported by Windows
(usually 96)
You can override the dpi value using the '-dpi' command line option.
[1] http://cygwin.com/ml/cygwin-xfree-announce/2010-04/msg00000.html
----------------XWin.0.log starting with with %RUN%
XWin.20100418-git-9594fb420a063608.exe -multiwindow -clipboard
-silent-dup-error -xkblayout gb -logverbose-------------------
Welcome to the XWin X Server
Vendor: The Cygwin/X Project
Release: 1.8.0.0 (10800000)
Snapshot: 20100418-git-9594fb420a063608
Contact: cygwin-xfree@cygwin.com
XWin was started with the following command line:
/usr/bin/XWin.20100418-git-9594fb420a063608 -multiwindow
-clipboard -silent-dup-error -xkblayout gb -logverbose
ddxProcessArgument - Initializing default screens
winInitializeDefaultScreens - primary monitor w 2560 h 1024
winInitializeDefaultScreens - native DPI x 96 y 96
winInitializeDefaultScreens - Returning
use: X [:<display>] [option]
[displays usage info]
--------------------------
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ: http://x.cygwin.com/docs/faq/