NO no, I get it, and yes, I know what you mean.
The issue comes from the fact that the loop timing is controlled by the button timeout. So when you hit a button, the timeout doesn't happen and the loop runs faster than it should.
I'm working out a solution for this, no worries. The best bet would be to extract the data logging from the GUI code, and that is certainly the future. But a quick fix may probably be in order for now
