-
Notifications
You must be signed in to change notification settings - Fork 228
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
Dialogs appear on different monitors in dual display setup #885
Comments
Can you try this for "a" key (run automatic analysis of game), for example?
|
Hi kaorahi, you mean fumble around in the code? I mean, I was a programmer, but I have no clue about Lizzie or what to do to make these changes... but I could try. But I see what you do there, that looks like it would be the fix. |
Would you test this if you can compile it? https://github.com/kaorahi/lizzie/tree/fix885_dual I dare to make the patch on #884 (patched 0.7.4) because we also need to fix several patches in #884 for #885. |
Is it the official build process described in https://github.com/kaorahi/lizzie/blob/fix885_dual/README.md ? Then I could try. |
Yes. Just two steps if the environment is ready.
|
I think I'm too stupid... I did |
Ah, my words were too few. Please forget my first post. You don't need to edit the source code by yourself. I checked all such flaws and made a fixed version. You may need to install some packages for Java beforehand. This step depends on your Linux distribution. In my case:
To test my fixed version, just open https://github.com/kaorahi/lizzie/tree/fix885_dual, click the green "Code" button, and click "Download ZIP". Then...
|
Yep, looks good! Thanks! |
Would it be possible to fix that? I have 2 monitors (running Linux), Lizzie main window is on the secondary screen. All dialogs (analyze-all, open, delete-node-warning ...) will still appear on the primary monitor. Would be so nice if they appear on the same monitor where the main window is located. Otherwise such a great tool, still my favorite for analysis.
The text was updated successfully, but these errors were encountered: