2 button keypad

2 button keypad

[bagleyd]

Hi

I am a long time user.  And I love the new 64 bit version seems to cleared
up all my virus scanner induced problems.

On two different laptops I noticed that -emulate3buttons 100 (or without
the 100) is ignored.  I don't have 2 button mouse only 2 button mousepads.
 This used to work.  For Toshiba, I don't know of a work around.  For my
Lenovo, I activated a middle button (but for consistency I would always
like the two button way to always work).  According to documentation its
deactivated if you don't have a 2 button button mouse... so a 2 button
keypad does not seem to qualify?  It seems to me it should never be
deactivated if someone requests it.

-- 
Cheers,
 /X\  David A. Bagley
(( X  bagleyd@tux.org     http://www.tux.org/~bagleyd/
 \X/  xlockmore and more

--
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: 2 button keypad

[Jon TURNEY]

On 30/09/2013 01:54, bagleyd@tux.org wrote:
> I am a long time user.  And I love the new 64 bit version seems to cleared
> up all my virus scanner induced problems.
> 
> On two different laptops I noticed that -emulate3buttons 100 (or without
> the 100) is ignored.  I don't have 2 button mouse only 2 button mousepads.
>  This used to work.  For Toshiba, I don't know of a work around.  For my
> Lenovo, I activated a middle button (but for consistency I would always
> like the two button way to always work).

-emulate3ubttons appears to work correctly for me.

> According to documentation its
> deactivated if you don't have a 2 button button mouse... so a 2 button
> keypad does not seem to qualify?  It seems to me it should never be
> deactivated if someone requests it.

The documentation for '-emulate3buttons' says that the *default* is to enable
that option if Windows reports a two buttons, otherwise disabled.

An explicit -emulate3buttons should always override the default.

Can you please provide your /var/log/xwin/XWin.0.log

-- 
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: 2 button keypad

[bagleyd]

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

Hi Jon

XWin.0.log says I have 5 mouse buttons.  But its lying. I just have 2
mouse pad buttons...  really.  :(

Here is my call:
C:\cygwin\bin\run.exe /bin/bash.exe --login  -c "xinit -- -scrollbars -ac
-clipboard -silent-dup-error -emulate3buttons 100 -unixkill"

I tried from reboot and it still says I have a mouse with 5 buttons.

It seems to me, Windows logs that I had a 5 button mouse at one time and
keeps thinking that I still do.  So it sends that info to XWin which in
turn disables my explicit call, thinking that since 5 != 2, I don't need
it.  (Even if I have 5 mouse buttons I still want to be able to click with
two buttons at the same time to activate middle button.  The reason is I
want both of my computers to behave consistently.)

Anyway it seems you can't trust Windows...

> On 30/09/2013 01:54, bagleyd@tux.org wrote:
>> I am a long time user.  And I love the new 64 bit version seems to cleared
>> up all my virus scanner induced problems.
>> On two different laptops I noticed that -emulate3buttons 100 (or
without
>> the 100) is ignored.  I don't have 2 button mouse only 2 button mousepads.
>>  This used to work.  For Toshiba, I don't know of a work around.  For
my
>> Lenovo, I activated a middle button (but for consistency I would always
like the two button way to always work).
>
> -emulate3ubttons appears to work correctly for me.
>
>> According to documentation its
>> deactivated if you don't have a 2 button button mouse... so a 2 button
keypad does not seem to qualify?  It seems to me it should never be
deactivated if someone requests it.
>
> The documentation for '-emulate3buttons' says that the *default* is to
enable
> that option if Windows reports a two buttons, otherwise disabled.
>
> An explicit -emulate3buttons should always override the default.
>
> Can you please provide your /var/log/xwin/XWin.0.log
>
> --
> Jon TURNEY
> Volunteer Cygwin/X X Server maintainer


-- 
Cheers,
 /X\  David A. Bagley
(( X  bagleyd@tux.org     http://www.tux.org/~bagleyd/
 \X/  xlockmore and more




[-- Attachment #2: XWin.0.log.txt --]
[-- Type: text/plain, Size: 3937 bytes --]

Welcome to the XWin X Server
Vendor: The Cygwin/X Project
Release: 1.14.3.0
OS: CYGWIN_NT-6.2-WOW64 zen 1.7.25(0.270/5/3) 2013-08-31 20:39 i686
OS: Windows 8  [Windows NT 6.2 build 9200] (WoW64)
Package: version 1.14.3-1 built 2013-09-16

XWin was started with the following command line:

X :0 

ddxProcessArgument - Initializing default screens
winInitializeScreenDefaults - primary monitor w 1366 h 768
winInitializeScreenDefaults - native DPI x 96 y 96
[1482975.546] Initializing built-in extension Generic Event Extension
[1482975.546] Initializing built-in extension SHAPE
[1482975.546] Initializing built-in extension MIT-SHM
[1482975.546] Initializing built-in extension XInputExtension
[1482975.546] Initializing built-in extension XTEST
[1482975.546] Initializing built-in extension BIG-REQUESTS
[1482975.546] Initializing built-in extension SYNC
[1482975.546] Initializing built-in extension XKEYBOARD
[1482975.546] Initializing built-in extension XC-MISC
[1482975.546] Initializing built-in extension XINERAMA
[1482975.546] Initializing built-in extension XFIXES
[1482975.546] Initializing built-in extension XFree86-Bigfont
[1482975.546] Initializing built-in extension RENDER
[1482975.546] Initializing built-in extension RANDR
[1482975.546] Initializing built-in extension COMPOSITE
[1482975.546] Initializing built-in extension DAMAGE
[1482975.546] Initializing built-in extension MIT-SCREEN-SAVER
[1482975.546] Initializing built-in extension DOUBLE-BUFFER
[1482975.546] Initializing built-in extension RECORD
[1482975.546] Initializing built-in extension DPMS
[1482975.546] Initializing built-in extension X-Resource
[1482975.546] Initializing built-in extension GLX
[1482975.546] (II) xorg.conf is not supported
[1482975.546] (II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information
[1482975.546] LoadPreferences: /home/bagleyd/.XWinrc not found
[1482975.546] LoadPreferences: Loading /etc/X11/system.XWinrc
[1482975.546] LoadPreferences: Done parsing the configuration file...
[1482975.562] winDetectSupportedEngines - DirectDraw installed, allowing ShadowDD
[1482975.562] winDetectSupportedEngines - Windows NT, allowing PrimaryDD
[1482975.562] winDetectSupportedEngines - DirectDraw4 installed, allowing ShadowDDNL
[1482975.562] winDetectSupportedEngines - Returning, supported engines 0000001f
[1482975.562] winSetEngine - Using Shadow DirectDraw NonLocking
[1482975.562] winScreenInit - Using Windows display depth of 32 bits per pixel
[1482975.687] winWindowProc - WM_SIZE - new client area w: 1350 h: 729
[1482975.703] winFinishScreenInitFB - Masks: 00ff0000 0000ff00 000000ff
[1482975.718] MIT-SHM extension disabled due to lack of kernel support
[1482975.718] XFree86-Bigfont extension local-client optimization disabled due to lack of shared memory support in the kernel
[1482975.734] (EE) AIGLX: No native OpenGL in modes with a root window
[1482976.000] (II) AIGLX: enabled GLX_EXT_texture_from_pixmap
[1482976.000] (II) AIGLX: Loaded and initialized swrast
[1482976.000] (II) GLX: Initialized DRISWRAST GL provider for screen 0
[1482977.000] winPointerWarpCursor - Discarding first warp: 675 364
[1482977.000] (--) 5 mouse buttons found
[1482977.000] (--) Setting autorepeat to delay=750, rate=21
[1482977.000] (--) Windows keyboard layout: "00000409" (00000409) "US", type 7
[1482977.000] (--) Found matching XKB configuration "English (USA)"
[1482977.000] (--) Model = "pc105" Layout = "us" Variant = "none" Options = "none"
[1482977.000] Rules = "base" Model = "pc105" Layout = "us" Variant = "none" Options = "none"
[1482977.000] winBlockHandler - pthread_mutex_unlock()
[1482977.015] winProcEstablishConnection - winInitClipboard returned.
[1482977.015] winClipboardThreadProc - DISPLAY=:0.0
[1482977.015] winClipboardProc - XOpenDisplay () returned and successfully opened the display.
[1482986.234] winWindowProc - WM_ENTERSIZEMOVE
[1482988.578] winWindowProc - WM_EXITSIZEMOVE

[-- Attachment #3: Type: text/plain, Size: 223 bytes --]

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