In that case, I'm inclined to believe the problem is in your code...by Galleon (no login)
I think if you wrote gfx256 from the beginning with a mouse input message queue reading approach it would have been easier than now having to convert it to using a mouse input messages approach. I do find it hard to track some of your code (especially in how it weaves into and out of the menu handler, sometimes entering a new loop and sometimes not), and this probably accounts for why I failed to correct the problem in my first attempt. I'm tempted to try again and use a more thorough approach. In testing I was able to get your _MOUSEINPUT version to totally miss mouse clicks, so that's a good place for me to start.
Whatever happens, don't feel bad about the time I might spend 'fixing' this, it is more important to me than to you that we get to the bottom of this. It is important to QB64.
|Response Title||Author and Date|
|*Thanks, Galleon -- I'm sure you're right.||on Jan 30|
|*Double post error -- ignore.||on Jan 31|
|Galleon, something I should mention ...||on Jan 31|
|*Noted.||Galleon on Feb 1|