Re: Getting cygwin-X client running with debian server.
On Sat, 16 Apr 2005 [EMAIL PROTECTED] wrote: Just a tip for newbies (like me) that try to get cygwin-X running with debian server. Apparantly the debian server's sshd default setting is not to forward X11. The error message I then get on my x-client is Can't open display. So the following setting in /etc/ssh/sshd_config is needed: X11Forwarding yes I didn't find this info in the faq, hence this note. What about this one http://x.cygwin.com/docs/faq/cygwin-x-faq.html#q-ssh-no-x11forwarding bye ago -- [EMAIL PROTECTED] http://www.gotti.org ICQ: 126018723
downgrade a 5-button- to a 3-button-mouse
We are running a propietary application on a tablet pc (windows XP Tablet-PC-Edition).. Most everything works, but there is a small glitch: For handling reasons some (function-)keys are combined into a small panel. Clicking the keys with the pen has no effect. Entering these keys with the virtual keyboard or a real attached keyboard works. From the support-line: This application DGK5 supports the configuration of a 3-button-mouse only. In Cygwin is a 5-button-mouse configured. You have to configure the Cygwin-X-server in such a way, that a 3-button-mouse is recognized. HOW? A Xfree-conf-file isn't used in Cygwin (AFAIK). -emulate3buttons has no effect, as it works the other way up (3 buttons on a 2-button-mouse). Any hints? Yours hjb
Re: downgrade a 5-button- to a 3-button-mouse
On Mon, 18 Apr 2005, Hermann-Josef Beckers wrote: We are running a propietary application on a tablet pc (windows XP Tablet-PC-Edition).. Most everything works, but there is a small glitch: For handling reasons some (function-)keys are combined into a small panel. Clicking the keys with the pen has no effect. Entering these keys with the virtual keyboard or a real attached keyboard works. From the support-line: This application DGK5 supports the configuration of a 3-button-mouse only. In Cygwin is a 5-button-mouse configured. You have to configure the Cygwin-X-server in such a way, that a 3-button-mouse is recognized. HOW? A Xfree-conf-file isn't used in Cygwin (AFAIK). -emulate3buttons has no effect, as it works the other way up (3 buttons on a 2-button-mouse). Cygwin/X will use a 3button mouse by default and ask windows how many additional buttons the mouse supports. I'm have no idea how these special function keys are supposed to work, but functions keys which depend on a mouse setting are broken in my opinion. You may check with xev if the keys are somehow recognized in Cygwin/X nevertheless. bye ago -- [EMAIL PROTECTED] http://www.gotti.org ICQ: 126018723
Antwort: Re: downgrade a 5-button- to a 3-button-mouse
[EMAIL PROTECTED] schrieb am 18.04.2005 15:39:43: Cygwin/X will use a 3button mouse by default and ask windows how many additional buttons the mouse supports. I'm have no idea how these special function keys are supposed to work, but functions keys which depend on a mouse settingare broken in my opinion. Problem is there is no real mouse, only the pen/stylus acting as a mouse. The mailinglist has a short thread (2 messages) from march 2003; Harold suggestesd using -multiwindow: it is activated, no chance. You may check with xev if the keys are somehow recognized in Cygwin/X nevertheless. Following are three xev-traces from entering the panel, clicking the button labeled F6 and leaving. Run 1: EnterNotify event, serial 13, synthetic NO, window 0x80051f, root 0x3a, subw 0x800533, time 1469359, (55,0), root:(141,374), mode NotifyNormal, detail NotifyNonlinearVirtual, same_screen YES, focus YES, state 0 KeymapNotify event, serial 13, synthetic NO, window 0x0, keys: 58 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 VisibilityNotify event, serial 13, synthetic NO, window 0x80051f, state VisibilityPartiallyObscured VisibilityNotify event, serial 13, synthetic NO, window 0x80051f, state VisibilityUnobscured ConfigureNotify event, serial 13, synthetic NO, window 0x80051f, event 0x80051f, window 0x80051f, (86,374), width 202, height 173, border_width 0, above 0x800427, override NO ConfigureNotify event, serial 13, synthetic NO, window 0x80051f, event 0x80051f, window 0x80051f, (86,374), width 202, height 173, border_width 0, above 0xa1, override NO ConfigureNotify event, serial 13, synthetic NO, window 0x80051f, event 0x80051f, window 0x80051f, (86,374), width 202, height 173, border_width 0, above 0x800427, override NO VisibilityNotify event, serial 13, synthetic NO, window 0x80051f, state VisibilityPartiallyObscured VisibilityNotify event, serial 13, synthetic NO, window 0x80051f, state VisibilityUnobscured KeyRelease event, serial 13, synthetic NO, window 0x80051f, root 0x3a, subw 0x0, time 1481218, (90,39), root:(176,413), state 0x0, keycode 8 (keysym 0x0, NoSymbol), same_screen YES, XLookupString gives 0 bytes: VisibilityNotify event, serial 16, synthetic NO, window 0x80051f, state VisibilityPartiallyObscured VisibilityNotify event, serial 16, synthetic NO, window 0x80051f, state VisibilityUnobscured VisibilityNotify event, serial 16, synthetic NO, window 0x80051f, state VisibilityPartiallyObscured VisibilityNotify event, serial 16, synthetic NO, window 0x80051f, state VisibilityUnobscured LeaveNotify event, seria Second try: EnterNotify event, serial 13, synthetic NO, window 0x80051f, root 0x3a, subw 0x800533, time 1569578, (159,14), root:(245,388), mode NotifyNormal, detail NotifyNonlinearVirtual, same_screen YES, focus YES, state 0 KeymapNotify event, serial 13, synthetic NO, window 0x0, keys: 58 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 LeaveNotify event, serial 13, synthetic NO, window 0x80051f, root 0x3a, subw 0x800533, time 1570375, (83,-12), root:(169,362), mode NotifyNormal, detail NotifyVirtual, same_screen YES, focus YES, state 0 ConfigureNotify event, serial 13, synthetic NO, window 0x80051f, event 0x80051f, window 0x80051f, (86,374), width 202, height 173, border_width 0, above 0xa1, override NO ConfigureNotify event, serial 13, synthetic NO, window 0x80051f, event 0x80051f, window 0x80051f, (86,374), width 202, height 173, border_width 0, above 0xa1, override NO EnterNotify event, serial 13, synthetic NO, window 0x80051f, root 0x3a, subw 0x800533, time 1571937, (112,13), root:(198,387), mode NotifyNormal, detail NotifyVirtual, same_screen YES, focus YES, state 0 KeymapNotify event, serial 13, synthetic NO, window 0x0, keys: 58 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 LeaveNotify event, serial 13, synthetic NO, window 0x80051f, root 0x3a, subw 0x800533, time 1572000, (222,81), root:(308,455), mode NotifyNormal, detail NotifyNonlinearVirtual, same_screen YES, focus YES, state 0 EnterNotify event, serial 13, synthetic NO, window 0x80051f, root 0x3a, subw 0x800533, time 1581203, (185,18), root:(271,392), mode NotifyNormal, detail NotifyNonlinearVirtual, same_screen YES, focus YES, state 0 Third try: EnterNotify event, serial 13, synthetic NO, window 0x80051f, root 0x3a, subw 0x800533, time 3836140, (162,1), root:(248,375), mode NotifyNormal, detail NotifyNonlinearVirtual, same_screen YES, focus YES, state 0 KeymapNotify event, serial 13, synthetic NO, window 0x0, keys: 58 0 0 0
Re: Antwort: Re: downgrade a 5-button- to a 3-button-mouse
On Mon, 18 Apr 2005, Hermann-Josef Beckers wrote: Problem is there is no real mouse, only the pen/stylus acting as a mouse. The mailinglist has a short thread (2 messages) from march 2003; Harold suggestesd using -multiwindow: it is activated, no chance. For windows there are basicly two input devices. Keyboards and mice. Keyboards will generate keypress and release events (WM_KEYDOWN). Mice produce button press and relese events (WM_[LMRX]BUTTONDOWN) for the left, middle, right and extra buttons. The WM_KEYUP has two kind of key information attached. The raw keyboard scancodes and the codes after applying the keyboard layout. Cygwin/X only uses the raw scancodes. If they don't match the real key it is very likely the key is not recognized. I've placed a small program on http://www.tu-chemnitz.de/~goal/xfree/msgtest.exe which will dump the messages to the console. Please run it and report what it prints when pressing the onscreen keys and what it reports when pressing the physical key. KeyRelease event, serial 13, synthetic NO, window 0x80051f, root 0x3a, subw 0x0, time 1481218, (90,39), root:(176,413), state 0x0, keycode 8 (keysym 0x0, NoSymbol), same_screen YES, XLookupString gives 0 bytes: This is just the release. There was no keypress event. Either some flags are wrong or the scancode was not right. bye ago -- [EMAIL PROTECTED] http://www.gotti.org ICQ: 126018723
Re: starting xterm from tcsh, gives error message: missing }.
Thanks Michael for the answer, you were correct.
It was a problem with spaces in the PATH. It is the script
/etc/profile.d/00xorg-x11-base.csh that does not handle the space. I
verified this by removing the part of the PAT that had the space in it.
The script is attached here in its original form. Hopefully someone who is
better than me at csh scripting can find a solution for future versions
of cygwin.
Bengt Svensson
$ more 00xorg-x11-base.csh
# The script name starts with 00 to ensure that it is executed before any
# other scripts because one of them may need to know where X is to run
# properly.
# Check if the PATH variable is empty or not
if ( $?PATH ) then
# PATH is not empty
# Check if path is already in PATH
eval /bin/echo ${PATH} | /bin/grep -q /usr/X11R6/bin
if ( $status ) then
# Path is not already in PATH, prepend it to PATH
setenv PATH /usr/X11R6/bin:${PATH}
endif
else
# PATH is empty
setenv PATH /usr/X11R6/bin
endif
On Fri, 2005-04-15 at 19:21 -0500, Bengt Svensson wrote:
I am using tcsh in cygwin and every time I start a new xterm from an existing
xterm/tcsh window I get the error message 'missing }.'
I recently updated my cygwin so everything should be current. But see attached
cygcheck -s -v -r output.
You haven't given enough context in that script to determine why that
line was problematic and I don't have a Cygwin install in front of me,
so I can't check.
To me that line looks fine as it was, however the purpose of the eval
was not obvious. I think that statement would be better without the
eval at all.
I notice that one directory in your PATH contains a space (c:\Program
Files\Common Files\MDL Shared\ISIS). If you examine your output from
cygcheck you will see that something weird is happening.
My guess is that at least one script in profile.d isn't handling
directories with spaces properly. They really should be rewritten to
use the $path variable instead ($path is an array, $PATH is a scalar) or
to explicitly set IFS and use proper quoting.
--
Michael Wardle [EMAIL PROTECTED]
