-
Notifications
You must be signed in to change notification settings - Fork 63
Windows' drivers have a focus problem. #872
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
Comments
Line 195 in 4e34157
This is okay. |
Also, this seems to be raising the previous plot: Line 462 in 4e34157
|
Tried to fix it: 3eb16a4
I simply removed the I found that when the third argument (show) is 0, then actually the window should be hidden, according to this: But instead, it seems like the current implementation tries to bring the window bottom (in the z-order). I don't know which one is the right behavior of IDL, so postponed fixing it... |
Having no ideas about IDL behavior, I'll make it behave the same as ubuntu GDL... Makes sense? |
Another fix: 77c3f03 |
Is this okay now? |
wshow,3,0 puts window 3 below all others. |
@GillesDuvert Thank you so much for clarifying this! Then the patched Windows driver behaves correctly. It never steals the focus from the GDL command line. |
One exception is when you fire up a new plot window using 'plot'. However at least wshow seems to work okay.. I will further investigate it. |
obsolete since #882 has been merged |
With new coding in GDL it has been possible to nearly replicate the desirable behavior of
keyboard focus without patching the plplot drivers, wingcc,c or wingdi.c.
Previously, keyboard focus was controlled solely by returning focus to the foreground
window. The foreground window was however changed in the original wingcc driver and so
un-doing this change via a patch in plplot allowed for a correct behavior:
(this patch was proposed and rejected by the plplot group)
The new interface to wingcc #864 works around this but it is somehow inadequate, failing the following test with multiple windows (can be .RUN or just executed with "@").
The text was updated successfully, but these errors were encountered: