Hello,
I am new here, so first of all thank you for this helpful tool.
I currently use version 1.2.3 on Windows XP Pro SP3.
I would like to submit the following enhancements and bug :
- Enhancement #1
Unless I did it wrong, currently, adding a new profile with the "Add new profile" button, makes a copy of the "default" profile, not the currently selected user profile. It does not easy creation of several variations of one user profile.
Could the "Add new profile" button create a copy of the currently selected profile would be great.
- Enhancement #2
The profile name currently only accepts alphanumerical characters and space. Please allow at least DOS characters for filenames.
- Bug
To circumvent the limitation listed in enhancement #1, I tried to save my user profile to disk as .ini file, click the "add profile button" to create a new profile from scratch and then try to reload the .ini profile, hoping it will "patch" the new profile (default) values with the .ini profile values. It just does not load anything ?!
- Enhancement #3
When using the save/load profile to/from disk buttons, the dialog box opens up in the document folder instead of the last save folder. Remembering the last save location for user profiles would be fine...
- Enhancement #4
When printing a document, PDFCreator always start with the default profile. It would be nice it could remember the last used profile...
Thank you.
Bug #2
the PDFCreator Cannot create single JPG / other Image files from a multipage Word Documents even when in the Options the following Option is enabled
Options -> Documents
[ ] Only One page per file ( Not for PDF and EPS files )
only one file will be created with a %d in the file name instead of the expected number
like FileName%d.jpg
Hello,
I am sorry, but your answer is not related to my post.
I am afraid you answered someone else post...
Regards.
someone! yes that's me
i agree with your bugs and enchancements but the question is how do we get the authors of the pdfcreator to enhance it ?
there have been many outstanding bugs that have not been fixed some as old as v 0.9.7 and now its v 1.2.3
Hello,
the bug #2 will be fixed in the next version. As for the other things: we will have a look at them. They all take some time, but don't sound as if they are impossible to do.
regards,
Philip