Re: fvwm ignores clickToFocus for function keys

Re: fvwm ignores clickToFocus for function keys

[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's the *unmapped* version of the function key.

Okay, here's the information I forgot to supply (or only hinted at): I use the xterm.VT100.Translations resource (in my .Xdefaults file) to map the function keys:

xterm*VT100.Translations: #override \n\
    <Key> Print: string(0x7f) \n\
    <Key> Pause: insert-selection(PRIMARY, CUT_BUFFER0) \n\
    Ctrl <Key> Prior: scroll-back(1,halfpage) \n\
    Ctrl <Key> Next: scroll-forw(1,halfpage) \n\
    \
    Shift <Key> Up: string(0x1b) string("OAA") \n\
    Shift <Key> Down: string(0x1b) string("OBB") \n\
    \
    Ctrl <Key> 3: string(0x1b) string("\\\\") \n\
    Ctrl <Key> 4: string(0x1b) string("_") \n\
    \
    Shift <Key> F7: string("/media/") \n\
    Shift <Key> F8: string("[<>|]") \n\
    Shift <Key> F9: string(0x1b) string("[35~") \n\
    Shift <Key> F10: string(0x1b) string("[36~") \n\
    Shift <Key> F11: string(" 2>&1 | ") \n\
    Shift <Key> F12: string(" 2>&1 | tee -a make.$md\n") \n\
    \
    Alt <Key> F2: keymap(vt100)\n\
    Alt <Key> F1: keymap(None)\n\
    \
    <Key> F1: string(0x1b) string("_") \n\
    <Key> F4: string("$ARCH/") \n\
    <Key> F5: string("../Include/%:t:r.hpp") \n\
    <Key> F6: string("../Source/%:t:r.cpp") \n\
    <Key> F7: string("->next") \n\
    <Key> F8: string("    ") \n\
    <Key> F9: insert-selection(PRIMARY, CUT_BUFFER0) \n\
    <Key> F10: string(" 2>&1 | ") \n\
    <Key> F11: string(" 2>&1 | head\n") \n\
    <Key> F12: string(" 2>&1 | less\n")

So, for example, if I hit F12 when the mouse cursor is outside the bounds of the window, ^[[24~ gets inserted onto my command line.



      

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: fvwm ignores clickToFocus for function keys

[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: This is typically used to work with local or remote X
	applications, integrated into your native Windows desktop, but
	controlled using the X window manager of your choice.

You're thinking of -multiwindow.

This topic really is X-specific.  It's more appropriate to use the
cygwin-xfree list, which handles Cygwin X issues and questions.  Please
follow-up there with any further replies.

Thanks,

-- 
Larry Hall                              http://www.rfk.com
RFK Partners, Inc.                      (508) 893-9779 - RFK Office
216 Dalton Rd.                          (508) 893-9889 - FAX
Holliston, MA 01746

_____________________________________________________________________

A: Yes.
> Q: Are you sure?
>> A: Because it reverses the logical flow of conversation.
>>> Q: Why is top posting annoying in email?

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: fvwm ignores clickToFocus for function keys

[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 same?
>
> Ah, you mean on cygwin and on linux?  Yes, that's the beauty of the thing.
>
> As far as a rootless X11 goes ... I don't know how to configure that.

Cygwin-X User's Guide to the rescue! :-)

<http://x.cygwin.com/docs/ug/configure.html>

-- 
Larry Hall                              http://www.rfk.com
RFK Partners, Inc.                      (508) 893-9779 - RFK Office
216 Dalton Rd.                          (508) 893-9889 - FAX
Holliston, MA 01746

_____________________________________________________________________

A: Yes.
> Q: Are you sure?
>> A: Because it reverses the logical flow of conversation.
>>> Q: Why is top posting annoying in email?

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: fvwm ignores clickToFocus for function keys

[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 and on linux?  Yes, that's the beauty of the thing.

As far as a rootless X11 goes ... I don't know how to configure that.



      

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: fvwm ignores clickToFocus for function keys

[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://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: fvwm ignores clickToFocus for function keys

[Morgan Gangwere]

[-- Attachment #1: Type: text/plain, Size: 1600 bytes --]

On Sun, 19 Sep 2010 13:03:19 -0700 (PDT)
Charles Smith <cts.private@yahoo.com> 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/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.

a) Are you running fvwm under a rootless X11?
b) are your configs the same?

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

Sounds like something is trashing a buffer... however I'm not entirely
sure.

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

See the 2 questions above...

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

Sounds oddly configuration related... then again, i don't use fvwm on
windows.

--~--
Morgan Gangwere

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

fvwm ignores clickToFocus for function keys

[Charles Smith]

[-- Attachment #1: Type: text/plain, Size: 1178 bytes --]

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.


      

[-- Attachment #2: cygcheck.out --]
[-- Type: application/octet-stream, Size: 118454 bytes --]

[-- Attachment #3: XWin.0.log --]
[-- Type: application/octet-stream, Size: 4701 bytes --]

Welcome to the XWin X Server
Vendor: The Cygwin/X Project
Release: 1.8.0.0 (10800000)
Build Date: 2010-04-02

Contact: cygwin-xfree@cygwin.com
XWin was started with the following command line:

X :0 

ddxProcessArgument - Initializing default screens
winInitializeDefaultScreens - primary monitor w 1400 h 1050
winInitializeDefaultScreens - native DPI x 96 y 96
winInitializeDefaultScreens - Returning
[ 30651.796] _XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6
[ 30651.796] _XSERVTransOpen: transport open failed for inet6/YK8J140188:0
[ 30651.796] _XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet6
[ 30652.375] (WW) Failed to open protocol names file /usr/lib/X11/protocol.txt
[ 30652.375] winValidateArgs - g_iNumScreens: 1 iMaxConsecutiveScreen: 1
[ 30652.375] (II) xorg.conf is not supported
[ 30652.375] (II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information
[ 30652.375] LoadPreferences: /home/mellman/.XWinrc not found
[ 30652.437] LoadPreferences: Loading /etc/X11/system.XWinrc
[ 30652.437] LoadPreferences: Done parsing the configuration file...
[ 30652.453] winGetDisplay: DISPLAY=:0.0
[ 30652.453] winDetectSupportedEngines - Windows NT/2000/XP
[ 30652.484] winDetectSupportedEngines - DirectDraw installed
[ 30652.484] winDetectSupportedEngines - DirectDraw4 installed
[ 30652.484] winDetectSupportedEngines - Returning, supported engines 00000007
[ 30652.484] winSetEngine - Using Shadow DirectDraw NonLocking
[ 30652.484] winAdjustVideoModeShadowDDNL - Using Windows display depth of 32 bits per pixel
[ 30652.656] winFinishScreenInitFB - Masks: 00ff0000 0000ff00 000000ff
[ 30652.703] Screen 0 added at virtual desktop coordinate (0,0).
[ 30652.718] MIT-SHM extension disabled due to lack of kernel support
[ 30652.718] XFree86-Bigfont extension local-client optimization disabled due to lack of shared memory support in the kernel
[ 30652.812] (II) AIGLX: Loaded and initialized /usr/lib/dri/swrast_dri.so
[ 30652.812] (II) GLX: Initialized DRISWRAST GL provider for screen 0
[ 30653.031] [dix] Could not init font path element /usr/share/fonts/TTF/, removing from list!
[ 30653.031] [dix] Could not init font path element /usr/share/fonts/OTF/, removing from list!
[ 30655.781] winPointerWarpCursor - Discarding first warp: 697 497
[ 30655.781] (--) 5 mouse buttons found
[ 30655.781] (--) Setting autorepeat to delay=500, rate=31
[ 30655.781] (--) winConfigKeyboard - Layout: "00000409" (00000409) 
[ 30655.781] (--) Using preset keyboard for "English (USA)" (409), type "4"
[ 30655.781] Rules = "base" Model = "pc105" Layout = "us" Variant = "none" Options = "none"
[ 30655.859] winProcEstablishConnection - Hello
[ 30655.859] winInitClipboard ()
[ 30655.859] winProcEstablishConnection - winInitClipboard returned.
[ 30655.859] winClipboardProc - Hello
[ 30655.859] DetectUnicodeSupport - Windows NT/2000/XP
[ 30655.875] winGetDisplay: DISPLAY=:0.0
[ 30655.875] winClipboardProc - DISPLAY=:0.0
[ 30655.890] winClipboardProc - XOpenDisplay () returned and successfully opened the display.
[ 30660.656] winClipboardFlushXEvents - unexpected event type 34
[ 30660.671] winClipboardFlushXEvents - unexpected event type 34
[ 38900.671] winShadowUpdateDDNL - IDirectDrawSurface4_Blt () failed: 887601c2
[ 38900.984] winShadowUpdateDDNL - IDirectDrawSurface4_Blt () failed: 887601c2
[ 38901.593] winShadowUpdateDDNL - IDirectDrawSurface4_Blt () failed: 887601c2
[ 38901.906] winShadowUpdateDDNL - IDirectDrawSurface4_Blt () failed: 887601c2
[ 38902.531] winShadowUpdateDDNL - IDirectDrawSurface4_Blt () failed: 887601c2
[ 38902.843] winShadowUpdateDDNL - IDirectDrawSurface4_Blt () failed: 887601c2
[ 38903.468] winShadowUpdateDDNL - IDirectDrawSurface4_Blt () failed: 887601c2
[ 38903.781] winShadowUpdateDDNL - IDirectDrawSurface4_Blt () failed: 887601c2
[ 38904.406] winShadowUpdateDDNL - IDirectDrawSurface4_Blt () failed: 887601c2
[ 38904.718] winShadowUpdateDDNL - IDirectDrawSurface4_Blt () failed: 887601c2
[ 38904.718] winShadowUpdateDDNL - IDirectDrawSurface4_Blt failure message maximum (10) reached.  No more failure messages will be printed.
[ 83495.437] winBltExposedRegionsShadowDDNL - IDirectDrawSurface4_Blt reported that the primary surface was lost, trying to restore, retry: 1
[ 89699.484] winBltExposedRegionsShadowDDNL - IDirectDrawSurface4_Blt reported that the primary surface was lost, trying to restore, retry: 1
[115961.765] winBltExposedRegionsShadowDDNL - IDirectDrawSurface4_Blt reported that the primary surface was lost, trying to restore, retry: 1
[119406.156] winBltExposedRegionsShadowDDNL - IDirectDrawSurface4_Blt reported that the primary surface was lost, trying to restore, retry: 1

[-- Attachment #4: Type: text/plain, Size: 218 bytes --]

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple