I don't feel this is a feature request or an enhancement. To me, it really is more of a bug or defect. The current behavior of the print-to-PDF functionality is unexpected for the user as it deviates from printing-to-printer and has no beneficial side effect. (i.e. there is no scenario, that I can see, that would benefit from current behavior over the, well, 'correct' behavior).
I suspect fixing this issue might not be all that difficult, I can imagine that the code does something like this:
FOR EACH SELECTED MESSAGE
OPEN PRINTING DEVICE OR FILE
PRINT MESSAGE
CLOSE PRINTING DEVICE OR FILE
END
This works well for actual printers, and would explain the current behavior with printing to PDF. It might be fixed by rewriting it too something like this:
OPEN PRINTING DEVICE OR FILE
FOR EACH SELECTED MESSAGE
PRINT MESSAGE
END
CLOSE PRINTING DEVICE OR FILE
Mind, this is a very high level description, and without looking at the actual code it remains to be seen if this is the root cause. However, I do think it is something like this.
Thanks again for your willingness to help with fixing this issue!
Hi GF,
I don't feel this is a feature request or an enhancement. To me, it really is more of a bug or defect. The current behavior of the print-to-PDF functionality is unexpected for the user as it deviates from printing-to-printer and has no beneficial side effect. (i.e. there is no scenario, that I can see, that would benefit from current behavior over the, well, 'correct' behavior).
I suspect fixing this issue might not be all that difficult, I can imagine that the code does something like this:
FOR EACH SELECTED MESSAGE
OPEN PRINTING DEVICE OR FILE
PRINT MESSAGE
CLOSE PRINTING DEVICE OR FILE
END
This works well for actual printers, and would explain the current behavior with printing to PDF. It might be fixed by rewriting it too something like this:
OPEN PRINTING DEVICE OR FILE
FOR EACH SELECTED MESSAGE
PRINT MESSAGE
END
CLOSE PRINTING DEVICE OR FILE
Mind, this is a very high level description, and without looking at the actual code it remains to be seen if this is the root cause. However, I do think it is something like this.
Thanks again for your willingness to help with fixing this issue!
Regards,
Orin