Back & foward button from mouse does not work.

Things you’d like to miss in the future...
Forum rules
When reporting a bug, please include the following information: your XYplorer version (e.g., v27.90.0047), your Windows version (e.g., Win 11), and your screen scaling percentage (e.g., 125%). We recommend adding your Windows version and screen scaling percentage to your profile or signature. This will make debugging much easier for us.
The_Dude
Posts: 45
Joined: 13 Sep 2005 08:24

Post by The_Dude »

I did some web searching... are you using WM_MOUSE messages to get the information? If so, then the following scrap of conversation may help:
The second item I could not process was the new X1 and X2 buttons found on the newer Microsoft IntelliMouse®. The problem was a lack of hardware on my part. ...the WM_XBUTTONxxx messages pass which button was pressed in the high order word of the wParam. Since the WM_MOUSEWHEEL message passes the wheel click direction in the same way...

admin
Site Admin
Posts: 64849
Joined: 22 May 2004 16:48
Location: Win8.1, Win10, Win11, all @100%
Contact:

Post by admin »

The_Dude wrote:I did some web searching... are you using WM_MOUSE messages to get the information? If so, then the following scrap of conversation may help:
The second item I could not process was the new X1 and X2 buttons found on the newer Microsoft IntelliMouse®. The problem was a lack of hardware on my part. ...the WM_XBUTTONxxx messages pass which button was pressed in the high order word of the wParam. Since the WM_MOUSEWHEEL message passes the wheel click direction in the same way...
I'm using WM_MOUSE messages to catch the mouse wheel; the standard buttons however are raised into VB native events. Looking for WM_XBUTTONxxx messages might be a way... I won't have time for this very soon, though.

Thanks anyway!

admin
Site Admin
Posts: 64849
Joined: 22 May 2004 16:48
Location: Win8.1, Win10, Win11, all @100%
Contact:

Post by admin »

The_Dude wrote:PS I believe that MS call those two buttons the X1 button and X2 button (if I am not confusing two different things).
Yes, correct. I'm now catching the XBUTTON messages via subclassing the form, but, damn it!, they are consumed by the controls covering the form. There's only a very tiny area (marked orange) where the form is exposed and the XButtons should work:
Image
Any ideas anybody?

admin
Site Admin
Posts: 64849
Joined: 22 May 2004 16:48
Location: Win8.1, Win10, Win11, all @100%
Contact:

Post by admin »

Just to close this thread: history buttons do work now perfectly. The case is closed. :)

Post Reply