Android: Different UI scaling after upgrading to 3.10.0
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 55/100
Research direction
Start by tracing AppSettings display scaling and the DISPLAY_SCALE_NATIVE_PIXELS mode, then reproduce the Android upgrade from 3.9.0-stable to 3.10.0-beta2 with the reported UI layout. Compare the reported resolution and display-density handling between versions. Done means existing layouts retain their 3.9.0 sizing and positioning without requiring setDisplayScaleMode(DISPLAY_SCALE_NATIVE_PIXELS).
Written by the indexing model from the issue text.
Description
This affected my android application. I don't know if it also affects desktop apps.
After upgrading android app from 3.9.0-stable to 3.10.0-beta2
- Some UI elements were 2 or 3 times the previous size
- Some UI elements did not appear at all (because their position was now outside the screen)
AI told me this:
// jME 3.10 divides the reported resolution (AppSettings/camera width+height) by the
// display density by default, even though DisplayScaleMode itself defaults to
// "disabled". Our GUI/HUD code assumes those are real framebuffer pixels like every previous
// jME version - request native-pixel mode to restore that 1:1 mapping.
Workaround:
After adding this call it worked OK as previously:
settings.setDisplayScaleMode(AppSettings.DISPLAY_SCALE_NATIVE_PIXELS);
The expected behaviour here is that the layout would work the same as in 3.9.0 without requiring code changes.
- Dominant language
- Java
- Stars
- 4.3k
- Forks
- 1.2k
- Avg merge
- 10h 57m
- Merged PRs (30d)
- 21
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
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.
More from jMonkeyEngine/jmonkeyengine
-
Documentation
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
jMonkeyEngine/jmonkeyengine#2928 · 4 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
jMonkeyEngine/jmonkeyengine#2919 · 1 comment ·
Maintainers usually reply within 1 day
-
defect
Difficulty 1/5 Under an hour Newbie friendliness 88/100
jMonkeyEngine/jmonkeyengine#2717 ·
Maintainers usually reply within 1 day
-
Documentation
Difficulty 3/5 1-2 days Newbie friendliness 57/100
jMonkeyEngine/jmonkeyengine#2930 · 3 comments ·
Maintainers usually reply within 1 day
-
Android: Mouse and Keyboard are no longer emulated by default in 3.10.0Possibly taken @riccardobl claimed this 37 days ago. Open
jMonkeyEngine/jmonkeyengine#2929 · 1 comment · 1 reaction · 2 assignees ·
Maintainers usually reply within 1 day
All issues in jMonkeyEngine/jmonkeyengine
Similar issues
-
Clock.MakeTime fails to validate hour, minute, and second ranges due to inert Calendar.set try-catchOpen
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
mit-cml/appinventor-sources#4139 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Vakore/ZappierGames#81 ·
-
proposal
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
beemdevelopment/Aegis#1843 · 1 reaction ·
-
[Bug] Logo style setting missing and `classic` style not applied across multiple platforms (v3.1.0)Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Stirling-Tools/Stirling-PDF#8382 · 1 reaction ·
Maintainers usually reply within 2 days
-
>enhancement needs:triage
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
elastic/elasticsearch#161191 ·
Maintainers usually reply within 1 day