-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Next MouseHit ignored after graphics change #27
Comments
I can confirm that it is flawed on Linux too. Hit the Mouse and it switches graphics. Next mouse hit is not registered (else it would switch graphics again). |
In brl.polledinput there is
|
Seems to work here, on Windows 10. |
It works here "randomly" too ... most of the time when clicking "very right" of the window ... when not moving the mouse much and staying in the center, doing "calm" mouse clicks (while checking the output pane for text output ) ... and it fails everytime. tried it on Linux. Edit: using "brl.glmax2d" instead and it works 100% of the time. |
One could try adding |
You mean that way:
If so then no, does not work ;-/ BTW I already tried with "alt + tab" to bring back and forward, minimize + restore ... did not repair the issue. Edit: Were you able to verify it on your linux box? |
Ok ... another uhm ... maybe it helps narrowing it down: I replaced the
So when opening the app and doing LMB and followed by RMB you see two switches - as you would expect. The RMB seems to not be properly "eaten" as the underlying Window receives an RMB event. Following to LMB + RMB you need to click each button once to make this button to work for one time again. |
The issue is that the "mouse up" event can get lost during the moment that no window exists - since the "mouse down" event is driving the cycle of closing one then opening another window. |
But shouldn't and "app minimize/resume" (or "alt tab") refresh all this mouse stuff anyways?
What "cycle" ? Think I do not understand you properly |
(excuse this ugly "delayed graphics switch"-approach). As Brucey stated, this would make it "work". Not sure if we still should fix it (like "resetting" events or so ?). |
Source: https://www.syntaxbomb.com/index.php/topic,8057.new.html#new
Ashmoor wrote:
The text was updated successfully, but these errors were encountered: