B
bikuta
I've been puzzling over this for a while.
I've created a print macro which allow for duplex printing. A brief skeleton
looks like this:
1. User selects printer
2. User selects paper type
3. Printer settings are applied
4. Print out document
Sometimes the printer would (seem to) prematurely print before the settings
have been successfully applied.
I've tried stepping through the code and at one stage I actually need to run
a macro within this macro. As I step through the code once reaching the run
macro command, the debugger just decides to run the rest of the application.
This seems strange as normally when you debug an application it would just
step through once the command is complete. By calling this external macro,
has this caused another thread to start or what?
Does anyone know why this behaviour occurs?
I've created a print macro which allow for duplex printing. A brief skeleton
looks like this:
1. User selects printer
2. User selects paper type
3. Printer settings are applied
4. Print out document
Sometimes the printer would (seem to) prematurely print before the settings
have been successfully applied.
I've tried stepping through the code and at one stage I actually need to run
a macro within this macro. As I step through the code once reaching the run
macro command, the debugger just decides to run the rest of the application.
This seems strange as normally when you debug an application it would just
step through once the command is complete. By calling this external macro,
has this caused another thread to start or what?
Does anyone know why this behaviour occurs?