Hi Christian,
Christian Junker schrieb:
there should be no interaction by the user at all. Then:Hi Peter,
should have tested this (again it shows that you should always test something before you give advice).
I thought again about your problem and if your script does not run all the time but only sometimes I would propose the following to you:
Either you create a dialog, or which is little bit more complicated a modular window (with the windowdescriptor service), that pops up when the macro begins its execution. In that time the user is caught in this one dialog (I would put an explanatory text like "Please wait until the progress finishes..." and if you want to make it professional you add some progressbar or some animation or whatever so that the user is occupied at least with something). The important thing is that the dialog itself has been "disabled" which means that it is not closed when the user presses the "X" button that you can see for every window on popular platforms.
You do that by setting the "enabled" property in the dialog properties to the value "off".
how to run a progressbar automatically after executing the dialog,
how to hide (EndExecute) a basic dialog without any user-interaction?
Which event should close it?
So I think you have to start an asynchron process before showing the dialog, which can do that.
I only know asynchron triggering in BASIC by callback-functions (e.g. the deprecated CHAOS-Module).
Peter
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
