Skip to content
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

multiple monitors - Entry Editor context menu always appears on main monitor even when Jabref isn't #6935

Closed
NRJank opened this issue Sep 23, 2020 · 2 comments

Comments

@NRJank
Copy link

NRJank commented Sep 23, 2020

JabRef 5.2--2020-09-21--0da0f0c
Windows 10 10.0 amd64
Java 14.0.2

On a two-monitor system, Jabref always opens on the last monitor it was on when it was closed, but the context menu for the Entry Editor seems to always only appear on whatever windows designates as the primary monitor. Tested with 5.1 and 5.2 (version above). Context menus for other things appear near the mouse pointer as expected.

Steps to reproduce the behavior:

  1. Open Jabref (appears on main monitor)
  2. right click on a database entry, context menu appears as expected near pointer.
  3. double click entry to open Entry Editor, right click one of the fields, context menu appears near pointer.
  4. move Jabref window to second monitor.
  5. right click on a database entry, context menu appears as expected near pointer.
  6. right click one of the Entry Editor fields, context menu appears back on main monitor, at closest edge to monitor with Jabref
  7. move Jabref back to main monitor
  8. right click in Entry Editor, context menu appears near pointer again.

Screenshot with context menu where it belongs:
Context menu where it belongs

Screenshot with context menu stuck on the right (main) monitor. (note the windows start bar starts again denoting monitor edge)
Context menu stuck on main monitor

Event log always blank

screenshots dont show it but in both cases mouse pointer was over the Title entry field.

@NRJank
Copy link
Author

NRJank commented Sep 24, 2020

somehow missed a very similar open issue #5941 that's tagged as a linux issue. so seems to be a cross-OS problem.

@calixtus
Copy link
Member

@NRJank thanks for reporting and for linking to the other issue. I'll mark this as duplicate, if that's fine for you. I have put the other issue report in our soon to fix bug list.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants