The application is meant to be installed and executed on machines where
there is no user interaction at all. So I cannot assume that someone will run
this separate application to record the settings. Also evertytime the
application is re-started someone will have to select the settings which
may not be possible/acceptable to the user.
Thanks again.
Thanks also for your workaround suggestion, but I cannot use it as
my
application is supposed to be exposed as an API from a dll with no
user
interaction/GUI at all. If you
> know
> any other
workaround where I do not have to invoke the Export Dialog at
all, please
do let me know.
you can invoke the export dialog from a normal
application and record the
export settings, then use them by the no-GUI
library (making the dialog not
show up, but just using the recorded
settings and maybe editing them on the
fly by using QTFindChildByID as
shown at
http://developer.apple.com/qa/qa2001/qa1147.html
)