jMonkeyEngine / jMonkeyEngine/jmonkeyengine

When the window size is bigger than the monitor's size, guiNode's translations mess up

Open
#732 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Contribution welcome Needs investigation
Dominant language
Java
Stars
4.3k
Forks
1.2k
Avg merge
4d 7h
Merged PRs (30d)
14

Description

jMonkeyEngine version: 3.2.0 alpha

For example, my desktop's monitor is 1980x1080, and when I set the window's height around 1060 or higher, the translations of guiNode's children are messed up. They work fine on full-screen mode (1980x1080).
guiNode's children whose y values are small are fine, but children with higher y values aren't placed properly.
The simplest way to test this would be to place something like BitmapText at the top of the screen (like this: https://anonimage.net/image/hHiwaZS5Qm) and it will be displayed properly until the window gets too tall for your screen (e.g., 1920x1080 windowed, due to the frame), for me the text got cut off.

I know that it probably isn't a good idea for the user to set the window size too big for their monitor, but I still don't want it to produce bugs like this. Hopefully someone more skilful than I could fix this.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the issue with guiNode children such as BitmapText in a windowed mode whose size exceeds the monitor, then compare the translations at small and large y values with fullscreen mode. Done means guiNode children remain correctly positioned and are not clipped when the window is too tall for the monitor.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
game-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.