Re: fvwm ignores clickToFocus for function keys

Re: fvwm ignores clickToFocus for function keys

[Charles Smith]

This conversation was transferred from the cygwin main list because Larry Hall said it was xfree-specific...

From: Morgan Gangwere <0 dot fractalus at gmail dot com>
> Sounds like something is trashing a buffer... however I'm not entirely
> sure.
...
> Sounds oddly configuration related... then again, i don't use fvwm on
> windows.

My suspicion is that it has to do with the cut-buffers/clip-board-mechanism, somehow.

I'd said previously that what gets sent (when a function key is pressed but the mouse cursor isn't over the in-focus window) is the unmapped version of the function key.  It might also be some earlier contents of the cut-buffer, or something like that.  I'm still trying to track it down.

Being able to cut-and-paste between windows and cygwin is important, and I'm glad that this evolving capability is so far along... but is it possible to disable it, at least for debugging purposes?



      

--
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/

Re: fvwm ignores clickToFocus for function keys

[Jon TURNEY]

On 26/09/2010 12:28, Charles Smith wrote:
> This conversation was transferred from the cygwin main list because Larry Hall said it was xfree-specific...
>
> From: Morgan Gangwere<0 dot fractalus at gmail dot com>
>> Sounds like something is trashing a buffer... however I'm not entirely
>> sure.
> ...
>> Sounds oddly configuration related... then again, i don't use fvwm on
>> windows.
>
> My suspicion is that it has to do with the cut-buffers/clip-board-mechanism, somehow.
>
> I'd said previously that what gets sent (when a function key is pressed but the mouse cursor isn't over the in-focus window) is the unmapped version of the function key.  It might also be some earlier contents of the cut-buffer, or something like that.  I'm still trying to track it down.
>
> Being able to cut-and-paste between windows and cygwin is important, and I'm glad that this evolving capability is so far along... but is it possible to disable it, at least for debugging purposes?

'man XWin' [1] documents the -noclipboard option.

[1] http://x.cygwin.com/docs/man1/XWin.1.html

-- 
Jon TURNEY
Volunteer Cygwin/X X Server maintainer

--
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/

Re: fvwm ignores clickToFocus for function keys

[Charles Smith]

> 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/or other actions).  When the mouse is positioned directly inside the window, the programmed action occurs normally.
> 
> 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.
> 
> Thus, if I have programmed the xterm F12 key to send:
> 
>   2>&1 | less <nl>
> 
> it is only received by bash if the mouse is positioned inside the window.  This is a problem if I entered a command (other key input obeys the clickToFocus directive) and then hit F12, and some unidentifiable garbage gets inserted.
> 
> 
> I can't verify that this is a cygwin problem, but hours of googling haven't revealed any mention of the problem at all, an any platform.
> 
> Interestingly, I just noticed that the arrow keys seem to work normally, regardless of the position of the mouse.  It's only the function keys that behave poorly.
> 
> 
> Any help will be appreciated.
> 


I keep discovering new things about this problem.  I'd said previously that under linux this did not happen.  Not quite true.

It turns out that it happens if my mouse is positioned over xterm's scroll bars!

If the mouse is over the in-focus window, or any other window, or the root, the function keys work properly.  But if the mouse is positioned over the scroll bars, it sends garbage!

Furthermore, I just discovered something even more interesting - if the mouse is positioned over the title bar, the cut buffer gets modified ... uh oh, this is starting to sound like a configuration issue... but that was all on linux (suse 10.3).

On cygwin it's wrong whenever the mouse is not over the in-focus window.



      

--
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/