Galleon, something I should mention ...by (Login qb432l)
... or perhaps, I should say, re-state in greater detail. These self-initiated left-button presses occur long after the mouse has been cleared. Sometimes there can be as much as a minute goes by with nothing occuring, during which time I swirl the mouse around through all the different screen locations so that the program navigates all possible code that tests for button presses. Then, suddenly, a left-button press is detected, followed by a legitimate execution of code. For example, let's say I have the brush tool selected and after a period of time, a "splotch" appears in the work area. If I click "Undo", the splotch disappears, which means that the "IF leftbutton" code was properly executed after a period of the mouse button being clear to all other button tests.
If it's my code -- and it very well might be -- then somewhere a line must alter the status of the left mouse button without its being pressed. As I mentioned before, this occurs with both QB64 mouse routines as well as CALL ABSOLUTE (though much less frequently with CALL ABSOLUTE).
Anyway, for what it's worth,
|Response Title||Author and Date|
|*Noted.||Galleon on Feb 1|