Re: fvwm ignores clickToFocus for function keys

2010-09-21 Thread Larry Hall (Cygwin)
On 9/21/2010 3:39 PM, Charles Smith wrote: Cygwin-X User's Guide to the rescue!:-) Okay, I'll give that a try ... except ... can I run FVWM rootless? Where will it go? Doesn't rootless mode mean that the Windows window manager is used? No. From the link to the documentation: Note:

Re: fvwm ignores clickToFocus for function keys

2010-09-21 Thread Charles Smith
> Cygwin-X User's Guide to the rescue! :-) Okay, I'll give that a try ... except ... can I run FVWM rootless? Where will it go? Doesn't rootless mode mean that the Windows window manager is used? BTW, I have identified what gets sent when the cursor is NOT inside the bounds of the window: it'

Re: fvwm ignores clickToFocus for function keys

2010-09-21 Thread Larry Hall (Cygwin)
On 9/21/2010 12:14 PM, Charles Smith wrote: This is different than the operation of fvwm under linux. In that case, an in-focus xterm takes function key input as well as other key input, regardless where the mouse cursor is. a) Are you running fvwm under a rootless X11? b) are your configs the

Re: fvwm ignores clickToFocus for function keys

2010-09-21 Thread Charles Smith
>> This is different than the operation of fvwm under linux. In that >> case, an in-focus xterm takes function key input as well as other key >> input, regardless where the mouse cursor is. > > a) Are you running fvwm under a rootless X11? > b) are your configs the same? Ah, you mean on cygwin an

Re: fvwm ignores clickToFocus for function keys

2010-09-20 Thread Charles Smith
> a) Are you running fvwm under a rootless X11? No, but I will try that at work tomorrow and report back > b) are your configs the same? The same as what? Sorry, I don't understand the question. -- Problem reports: http://cygwin.com/problems.html FAQ: http://

Re: fvwm ignores clickToFocus for function keys

2010-09-19 Thread Morgan Gangwere
On Sun, 19 Sep 2010 13:03:19 -0700 (PDT) Charles Smith wrote: > When typing in an in-focus xterm, but the mouse cursor is elsewhere, > if I hit a function key, the programmed action does not occur. > Instead, something else occurs, which I cannot identify (involving > insertion of characters and