When a blank PDF dialog is opened from "New" in Explorer right-click menu, the settings are not saved. SOLVED

[rakunavi]

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

Hello all,

When a new document is created from "With Blank Pages" from the File menu, the page size and number of pages in the dialog are saved and will be displayed as default values the next time they are set. Starting with Build 380, custom settings can also be saved, making it more convenient.

• PDF-XChange Editor Version History - Build 10.1.0.380 (05 Sep 2023)
  Added the ability to create "presets" for paper sizes in the "Create New Document" and "Insert Empty Pages" dialogues. (T#6438)

• figure.png

However, when an empty document file is created from the "New" in the Windows Explorer right-click menu while the application is not yet running, the same dialog appears, but the settings are not saved. Page size, number of pages, custom settings, whatever can be set in the dialog. This is probably a limitation on the Windows, but if it is possible, it might be better if the settings are saved in the same way as when the application is launched.

• Animation.gif

Hoping that the above information will be of some help to you.
Thank you so much for your continued support.

Best regards,
rakunavi

- PDF-XChange Editor Plus Version: 10.1.0 build 380
- OS Version: Windows 11 Home 22H2 Build 22621.2134
- PC Model: Lenovo IdeaPad C340-15IWL, HP All-in-One 22-c0xx

[Daniel - PDF-XChange]

Hello, rakunavi

I suspect that this has to do with the fact that the editor is not fully opening for this action, and we save these settings to the registry while closing the software. I am unsure if it is possible to change this, but I will run it by the dev team.

Kind regards,

[rakunavi]

Hello Daniel,

I have confirmed that the update in build 381 has improved the situation. I would like to thank the support and developers for the quick response.

Best regards,
rakunavi

[Dimitar - PDF-XChange]