Maximizing an image window on a secondary monitor results in it being placed on primary monitor
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 786
- Forks
- 267
- PR merge metrics
- No merged PRs in 30d
Description
Tested on 1.53k.
This appears to be caused by `ImageWindow#getMaximumBounds`' usage, as it is passed to `Frame#setMaximizedBounds`. The `Rectangle` returned specifies a window location on the primary screen, causing the maximized bounds to require window presence on that screen.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with ImageWindow#getMaximumBounds and trace how its Rectangle is passed to Frame#setMaximizedBounds. Reproduce the issue by maximizing an image window on a secondary monitor, then verify that the maximized window remains on that monitor rather than being placed on the primary screen.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100