This works as expected.
Sometimes you need to bounce back to the previous screen once or twice to trigger the problem?
That a machine only has trouble with a single program does not prove that the fault lies with the program.
Perhaps, but it does strongly point the finger towards the software in question. And particularly as it only started happening recently after I moved up to the newer builds.. and that I can replicate it 100% here. Perhaps I should roll back and try to find a build where this doesn't occur?
I should also note that I am seeing this on both the PCs in my office...
Each program creates a unique set of circumstances that the machine must deal with.Not a problem.
My own career was in software engineering so I understand the mechanics. And when I say it "was", it was only cut short as a personal choice due to a very successful venture giving me the freedom to continue or not.
You "complain" nicely. I can understand your frustration.
OK, thanks, that's good to hear.
How about doing a set of screen shots and uploading them to pix01, so we can see exactly what you're doing?
OK, I'll look at that for you.
Mark