Pole display support broken in 6.13

[Guest]

In version 6.13 of POS, something containing the phrase "TRANSACTION NUMBER" seems to be written to POLE.DAT for a second, and then it writes the correct information back to the file. It writes the correct info quickly enough that I cannot put the contents of the file here, but it's long enough to crash my customer display. Have gone back to 6.10.

Thanks for all your hard work!

[Guest]

This happens when you press "+" after all items have been rung.

[CBL]

I assume that this happens to pass the transaction number from POS to the Remote Viewer. If you are using PCdsp, it has now been updated to cope with this.

[Dale Harris]

The "Transaction number" thing was added to the pole display output for the "remote" program to display. However right after sending out the "Transaction number" something else is sent to the pole display and I guess that it is too quick for the pole display to handle.

I will remove the "Transaction number" thing in the next version (being tested now) and that should fix the problem.