When Autoscroll command is executed in a multi-window setup, buttons in other windows may be pressed unintentionally

[rakunavi]

Hello all,

I have found that when the Autoscroll command (ID: cmd.view.layout.autoScroll) is executed with multiple windows open, button faces other than the operating window are also unnecessarily pressed.

PDF-XChange Editor commands are divided into two types: those that work only for the operated window (hereinafter referred to as Type A) and those that work for all windows (hereinafter referred to as Type B).

For example, in the Page Display group of the View tab, the commands in the first column from the left correspond to the former and those in the second column from the left to the latter.

• Type A commands
  • Rulers
  • Grid
  • Guides
  Type B commands
  • Thin Lines
  • Transparency Grid
  • Page Size/Position

• figure.png

When multiple windows are opened, each window has its own ribbon, but when a Type A command is executed, only the button face of the command in the window being operated on is pressed. In contrast, Type B commands will cause the button face of the command in all windows to be pressed.

Autoscroll, which belongs to the Page Display group on the View tab, is Type A in terms of its functionality, but as mentioned earlier, it is Type B because the button faces of commands other than the window in which the operation was performed are also unnecessarily pressed. Judging from the actual behavior, it seems more natural for the button surface to conform to Type A behavior.

• Animation.gif

I am afraid this is a very trivial matter, but I would like to inform you of it for your information.
Thank you so much for your continued support.

Best regards,
rakunavi

- PDF-XChange Editor PRO Version: 10.6.0 build 396
- OS Version: Windows 11 Pro / Home 24H2 Build 26100.3775
- PC Model: GMKtec Nucbox M7 Pro with HUION Kamvas Pro 19 / Lenovo IdeaPad C340-15IWL

[Daniel - PDF-XChange]

Hello, rakunavi

Thank you for the report, I have passed this along to the Dev team for review.

[confirmed by Vasyl]
This will be fixed in the next release (397), no ticket was needed

Kind regards,