[Version 11.0.0] Hide extension in filename field of the new custom 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,

Since version 11.0.0, we can now use the custom dialog boxes to open/save files and select folders.

However, I noticed that even when the file extension visibility is disabled in the settings, the file extension still appears in the filename field. When using the traditional system dialog, disabling the extension visibility correctly hides it from the filename field.

• figure.png

When saving a file, there is a risk that the user might accidentally change or delete the file extension. Furthermore, when opening a file by typing the filename from the keyboard, the user must include the extension, which is quite inconvenient.

No matter how much I think about it, I cannot see the need to require the file extension in the filename field; therefore, I believe that, at the very least on this point, custom dialogs should behave the same way as standard system dialogs.

What do you think about this improvement?

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 reproduce the issue and passed it along to the Dev team for review. We will be making some further changes in this area for the next release, so please do keep an eye on it.

Kind regards,

[rakunavi]

Hello Daniel, thank you for contacting developers.

In Version 11.0.0, a new custom file‑save dialog was introduced. However, I noticed that its behavior differs slightly depending on the type of file being saved—even though the action being performed is the same (saving a file).Specifically, the behavior varies between saving FDF/XFDF files (such as when exporting comments or links) and saving PDF files.
This observation assumes that the “Show file extensions” option is disabled in both cases.

For example, when saving an XFDF file, the “File name:” field displays a default filename with its extension (e.g., “output.xfdf”), even though the “Show file extensions” option is disabled.

At this point, depending on how the file extension is edited in the filename field, the behavior falls into the following four cases:

Case 1: Remove the extension from the default filename (e.g., “output”)

• → The file cannot be saved

Case 2: Enter an extension other than XFDF that is registered in Windows (e.g., “output.txt”)

• → An invalid file is generated

• figure1.png

Case 3: Enter an extension other than XFDF that is not registered in Windows (e.g., “output.xxx”)

• → An error message appears

• figure2.png

Case 4: Keep the correct XFDF extension (e.g., “output.xfdf”)

• → A valid XFDF file is generated

• figure3.png

Animation1.gif

Applying the same classification to saving a PDF file results in the following:

Case 1: Remove the extension from the default filename (e.g., “output”)

• → The PDF extension is automatically restored, and a valid PDF file is generated

Case 2: Enter an extension other than PDF that is registered in Windows (e.g., “output.txt”)

• → The file is saved with the specified (non‑PDF) extension, but the file itself is still a valid PDF

Case 3: Enter an extension other than PDF that is not registered in Windows (e.g., “output.xxx”)

• → The file is saved with the specified (non‑PDF) extension, but the file itself is still a valid PDF

Case 4: Keep the correct PDF extension (e.g., “output.pdf”)

• → A valid PDF file is generated as expected

Animation2.gif

In other words, when saving XFDF files, only Case 4 results in a proper XFDF file, whereas when saving PDF files, all four cases produce a valid PDF file—the only difference being the extension applied to the filename.

This is a minor detail, but since both dialogs serve the same purpose—saving a file—it seems preferable for their behavior to be consistent. I am sharing this observation for your reference.

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

[Sean - PDF-XChange]

Hi Rakunavi,

Thanks for the report, I have let the team know and they are on the case.

Kind regards,