Hi,
I'm not sure it makes sense to have a UNO interface for the printer
dialog. It basically has to be implemented in vcl, since the result it
produces needs to be a vcl JobSetup. Which contains a binary system
dependent blob that can only be interpreted by the platform specific
print system in vcl's platform layer anyway. The crux here is the
equivalent to the current "Properties" button in the print dialog which
basically runs a native system dialog (well, on Windows and OS2 anyway).
Since the dialog implementation is necessarily married to the vcl
platform dependent print system anyway, I don't think making this dialog
a component will be really helpful.
For alternate methods of using the native print dialog see e.g. the
current Mac/Aqua implementation (which is quite radically different).
Speaking of Mac/Aqua printing we need to remodel printing anyway, but
that may be another story.
I imagine that integrating the dialog directly into vcl will probably be
more flexible.
Just my 2 cents, pl
Caolan McNamara wrote:
Any comments on this initial attempt to make an idl for the printer
dialog to form a basis of uno-ifying the dialog ?
Might be ok to remove the FromTo stuff, we have references to the old
version of this spread throughout our existing code, but the current
dialog doesn't actually implement it so it never kicks in.
C.
--
If you give someone a program, you will frustrate them for a day;
if you teach them how to program, you will frustrate them for a lifetime.
-- Author unknown
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
