Here the user can then decide via Yes/No whether to save or not. If the flag is set and a PDF is closed, a message is displayed stating that this PDF has not yet been saved. If a form field in a PDF is modified, the PDF is marked as modified. In this way, the saved default settings of the printer are applied. The print dialog is initialized with the settings of the default printer when the user clicks on the print icon.

Reader: Initialization of the print dialog improved Whenever saving or printing, we force the focus to be removed beforehand so that the changes in the field are saved and printed as well. If a form field was changed, the focus was left in the field and then saved or printed, then the changes from this field were not saved or printed. In PDF24 Reader there was still a problem with form fields. Reader: Changed form fields, focus in the field and subsequent saving/printing In the Excel to PDF function, we clear the SaveChanges flag to prevent a possible dialog here as well. In the end we just export a PDF without changing the actual file. Why the dialog sometimes appears and sometimes not is still unclear.

Word to PDF automation now sets the wdDoNotSaveChanges flag when closing a file to prevent a save dialog at the end which blocks the whole conversion process. See the manual for more information.ĭocTool: Word to PDF and Excel to PDF issue fixed The code parts responsible for hiding functions/tiles in the Toolbox have been improved and more metadata has been added to allow more functions to be disabled via the Windows registry. In the toolbox, there are changes in this area and an admin can now configure the toolbox or the visible tiles more easily.Ĭommon: Code parts for hiding functions extended The new code makes the query a bit more flexible, which also makes it easier for admins to configure.

Common: Code for querying the feature status optimized

Free PDF24 Creator 11.13.1