Does the script always miss the same ticket(s)?
No, it prints a ticket in the queue, sometimes more than one from the queue, but always with 2 blank sheets per ticket.
I realised I forgot the actual print script so here it is
Picking2.pdf 243.4 K
1 of 1 people found this helpful
when running the script with the Debugger do you run step by step ? If so that could mean a timing problem (I haven't look at your scripts). One way to debug that kind of issue is to use the successive approximation method:
- Run step by step for the 1st half of the script.
- If the issue happens, you know it's in the 1st half.
- If the issue did not occur, the run the scritp up to the half, and then run step by step.
This way you know in which half does the issue occur, and you can further converge to the offending step.
Divide and conquer. Excellent suggestion!
If I run the scripts to create the picking tickets in the Degugger it all works perfectly even when I run the print script in real time. I suspect a timing issue of the script to create the Picking Header (PickHead) Any ideas how to overcome timing errors?
Thanks a lot
the Debugger may be running a script a little bit slower. Was the script open in the Script Workspace at the same time ? That make running slower even further, you see the Workspace 'flashing'.
Another way to find where the delay would be needed is to put a pause for 1 sec at the end of a 'part' like right after a find. Don't insert many pauses, just move the one added if that doesn't solve the issue. Once you get to a location where issue disappear, you may move back the pause a few script step further to see if you can get closer to the step that needs a pause.