-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
remember location of earlier position of jabref window on displays #7341
Comments
Do you detach the monitors (e.g external monitor for a notebook) or do you have them permanently connected to your computer? Refs #5037 |
I have three monitors, running via gnome/Linux, Fedora 33. The cables between monitors and computer are always connected. current behaviour: When I quit JabRef, it always reappears on the same monitor. It also appears on that same monitor if I designate another display as a primary display. |
still of interest |
There might be some fix coming with the next javafx version |
Can you still reproduce? |
Hi, now on the issue is still present. JabRef works well, but it does neither recall its last position, nor does it follow Gnome's typical window placing policy (that is, the window should be placed on the display on which the mouse cursor is located). |
Still an issue JabRef 5.10--2023-01-12--5d24847 |
Doesn't the latter contradict with the former? Should JabRef "just" open at the last position (depending on the number of connected screens) or should it reposition itself on the monitor where the mouse curser is placed (and use the last position on that screen)? |
Yes, the contradiction is correctly identified. The point is that I would expect either of both options: either JabRef should show up where I last moved it, or it should show up as per Window Manager default (on Gnome, follow the current cursor). |
running Linux, Fedora 33, wayland.
JabRef 5.3--2021-01-13--4d8e4f0
Linux 5.9.16-200.fc33.x86_64 amd64
Java 15.0.1
JavaFX 15.0.1+1
I use several monitors. I am frustrated because JabRef forgets its location to which I had moved it before when it starts anew. Solution: remember location.
The text was updated successfully, but these errors were encountered: