[Version 11.0.0] Double-clicking window background passes the second click into the new custom "Open File" dialog box SOLVED

[rakunavi]

=== UPDATE ===================================================================
The issue reported below has been resolved in Ver 11.0.1.
I appreciate all the hard work and efforts of the support and development team.
==============================================================================

Hello all,

I would like to report an issue regarding the behavior of the new custom dialog in version 11.0.0.

In PDF-XChange Editor, when no files are open, double-clicking the window background opens an existing document. Previously, this action opened the standard system dialog. However, starting with version 11.0.0, the new custom dialog appears by default.

I noticed that when this custom dialog is enabled, the second click of the double-click registers inside the newly opened dialog, affecting its UI elements.

Normally, the double-click action should only trigger the opening of the dialog. No matter where you double-click on the background, it should not affect the subsequent dialog. However, the second click of the double-click is being treated as an active click at that exact screen position inside the custom dialog.

In the attached video, I am double-clicking the window background to open the custom dialog while slightly changing the mouse cursor position each time. You can see that the selected folder inside the dialog changes depending on where I double-clicked.

• Animation.gif

Please note that if I change the settings back to the classic system dialog, double-clicking simply opens the dialog as expected without unintentionally altering folders or selecting anything.

Could you please look into this issue?

Best regards,
rakunavi

- PDF-XChange Editor PRO Version: 11.0.0
- OS Version: Windows 11 Pro / Home 25H2 Build 26200.8457
- 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 reproduced this issue as well, and passed it along to the Dev team for review.

Kind regards,