Page 1 of 1

Compatible issues with strokeplus

Posted: 19 Apr 2026 05:42
by qwerty
I’m using StrokePlus (mouse gesture app) together with XYplorer and ran into an issue with recent beta versions.

I have a gesture mapped to minimize the current window using:
acMinimizeWindow(nil, gsx, gsy) => StrokePlus function

This function relies on the current mouse position to detect the target window. Up to around version 28.29.xxx, it worked perfectly with XYplorer regardless of where the gesture started—whether over the left pane, right pane, or other UI areas.

However, after upgrading to a 28.30.xx beta (I’m not sure of the exact build where this changed), the behavior is different:
  • The gesture only works when started over the main window UI (e.g., title bar or status bar).
  • If the gesture starts over the left or right pane, it no longer minimizes the window.
  • Other gestures (e.g., creating a new tab) still work fine from those panes.
It seems like, in the newer beta, the left and right panes might no longer be treated as part of the main window for this type of window detection.

Anyone knows if this is an intentional change or a regression?

Re: Compatible issues with strokeplus

Posted: 19 Apr 2026 06:10
by jupe
Does it make a difference if you change this setting?

Configuration | General | Menus, Mouse, Usability | Usability | Highlight hovered items

Re: Compatible issues with strokeplus

Posted: 19 Apr 2026 06:13
by qwerty
no change

Re: Compatible issues with strokeplus

Posted: 19 Apr 2026 06:18
by jupe
And if you disable either of these temporarily, still no change?

Configuration | Information | File Info Tips & Hover Box | Show Hover Box

Configuration | General | Menus, Mouse, Usability | Mouse | Point to select

Re: Compatible issues with strokeplus

Posted: 19 Apr 2026 06:31
by qwerty
I disabled or enabled either one or both, but still no luck :cry:

Re: Compatible issues with strokeplus

Posted: 19 Apr 2026 06:38
by jupe
Not sure if you use single click, but that is the only other thing I can think of that has had recent changes that could possibly be related:

Configuration | General | Menus, Mouse, Usability | Mouse | Single-click to open an item

Re: Compatible issues with strokeplus

Posted: 19 Apr 2026 09:11
by admin
:maf: Something concerning gestures broke (very likely) in v28.30.0103 - 2026-04-10 15:42.

1) Can you confirm that this version (v28.30.0101 - 2026-04-09 18:51) still works?: viewtopic.php?p=237004#p237004

2) Is the gesture also broken when you perform it solely over the tree?

Re: Compatible issues with strokeplus

Posted: 19 Apr 2026 17:18
by qwerty
@admin, @jupe, thanks so much for your help.

I did extensive testing and was able to narrow down the issue to specific settings and versions.

It appears that the setting HighlightHoveredItems=1 (line 537 in the .ini file) interferes with the gesture behavior in versions v28.20.0605 through v28.30.0101. Setting HighlightHoveredItems=0 resolves the issue in these versions. This has been confirmed on the following builds:
  • v28.20.0605
  • v28.30.0000
  • v28.30.0001
  • v28.30.0100
  • v28.30.0101
However, starting from v28.30.0103, the gesture no longer works regardless of the HighlightHoveredItems setting. That is why it didn't work for @jupe's suggestions.
admin wrote: 19 Apr 2026 09:11 :maf: Something concerning gestures broke (very likely) in v28.30.0103 - 2026-04-10 15:42.

2) Is the gesture also broken when you perform it solely over the tree?
It works on the tree, the CatLog, and any other main window UI elements including even the tabs for the panes except the left or the right pane itself.

Hope this helps narrow down the root cause.

Re: Compatible issues with strokeplus

Posted: 20 Apr 2026 09:09
by admin
Thank you, that's interesting info!
qwerty wrote: 19 Apr 2026 17:18 It appears that the setting HighlightHoveredItems=1 (line 537 in the .ini file) interferes with the gesture behavior in versions v28.20.0605 through v28.30.0101. Setting HighlightHoveredItems=0 resolves the issue in these versions. This has been confirmed on the following builds:
Are you saying (implying) that the setting HighlightHoveredItems=1 (line 537 in the .ini file) did not interfere with the gesture behavior before version v28.20.0605?

PS: anyway, I'll try a new fix of the original problem (Jumping to the next Hover Box by arrow keys did not work when the mouse cursor was over the current Hover Box and "Configuration | General | Menus, Mouse, Usability | Usability | Highlight hovered items" was disabled.) in the next beta. That should end the issues with gesture apps. :beer:

Re: Compatible issues with strokeplus

Posted: 20 Apr 2026 14:00
by qwerty
admin wrote: 20 Apr 2026 09:09
Are you saying (implying) that the setting HighlightHoveredItems=1 (line 537 in the .ini file) did not interfere with the gesture behavior before version v28.20.0605?
No, I hadn’t tested any builds prior to v28.20.0605.

I’ve now spot-checked several earlier versions and confirmed that v27.00.0906, v27.90.0050, v28.10.0100, v28.10.0400, v28.20.0200, and v28.20.0600 all exhibit the same issue. In each case, it can be resolved by setting HighlightHoveredItems=0.

It’s possible that all x64 builds prior to v28.30.0103 are affected.

Re: Compatible issues with strokeplus

Posted: 20 Apr 2026 14:03
by admin
The next beta will fix it independently of HighlightHoveredItems, so it will fix a very old issue.

Re: Compatible issues with strokeplus

Posted: 20 Apr 2026 14:05
by qwerty
Another interesting finding: no similar issue has been observed in the x86 builds. In other words, the gesture app works as expected regardless of the HighlightHoveredItems setting. This has been confirmed in the x86 builds v26.90.0309, v27.00.0500, v27.10.0604, and v27.20.1208(the latest version).

This issue may have been introduced from the very beginning of the transition from x86 to x64.

Re: Compatible issues with strokeplus

Posted: 20 Apr 2026 14:18
by admin
Aha! That would explain why I didn't hear about it earlier.

Re: Compatible issues with strokeplus

Posted: 20 Apr 2026 14:19
by qwerty
admin wrote: 20 Apr 2026 14:18 Aha! That would explain why I didn't hear about it earlier.
:tup: :tup: :tup: