I have a project where I have the __UI_BeforeUpdateDisplay loop, the __UI_Click loop and a Calculations loop (in its own subroutine).
Inside the __UI_BeforeUpdateDisplay loop, there is a Condition A which may become True, and if so it sets a Flag to inform the Calculations loop.
There is a Button which when clicked will reset the Flag and will alter things in the __UI_BeforeUpdateDisplay loop so that Condition A will be False.
If I were not doing this in InForm, my Mouse Polling would be at the start of the equivalent of the __UI_BeforeUpdateDisplay loop so that timings always ensure the Flag is reset at the correct moment and that the Condition A is False.
However, suppose in the Inform situation, the Mouse is clicked part way through the __UI_BeforeUpdateDisplay loop. The Flag would be reset, but at the end of that __UI_BeforeUpdateDisplay loop cycle the Condition A has still been True and therefore sets the Flag again.
I hope that you've get all that! How does InForm Mouse Polling ensure that Click events do not occur 'part way through' the __UI_BeforeUpdateDisplay loop? I suspect that this is another of my dumb questions. In the actual program, the Reset Click always works properly.
Richard