Opened 5 years ago
Last modified 5 years ago
#20934 closed defect
JOSM display is just a mess — at Version 3
| Reported by: | Owned by: | team | |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Core | Version: | |
| Keywords: | template_report | Cc: |
Description (last modified by )
What steps will reproduce the problem?
- Selecting a menu, or opening a popup box.
What is the expected result?
What happens instead?
Screen, menus and popup boxes are just a mess. I have a screen shot I wanted to attach, but where do I put this??.
Please provide any additional information below. Attach a screenshot if possible.
Have to shut down JOSM and restart. Sometimes it will work fine for a while, at other times everything is messed up as soon as I try to select something in a menu or open a data entering box. How can I attach a screen shot??
URL:https://josm.openstreetmap.de/svn/trunk Repository:UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b Last:Changed Date: 2021-04-27 20:35:33 +0200 (Tue, 27 Apr 2021) Build-Date:2021-04-27 21:58:39 Revision:17833 Relative:URL: ^/trunk Identification: JOSM/1.5 (17833 en) Windows 10 64-Bit OS Build number: Windows 10 Pro 2009 (19042) Memory Usage: 870 MB / 1820 MB (384 MB allocated, but free) Java version: 1.8.0_291-b10, Oracle Corporation, Java HotSpot(TM) 64-Bit Server VM Look and Feel: com.sun.java.swing.plaf.windows.WindowsLookAndFeel Screen: \Display0 2560×1440 (scaling 1.00×1.00) Maximum Screen Size: 2560×1440 Best cursor sizes: 16×16→32×32, 32×32→32×32 System property file.encoding: Cp1252 System property sun.jnu.encoding: Cp1252 Locale info: en_NO Numbers with default locale: 1234567890 -> 1234567890 Dataset consistency test: No problems found Plugins: + imagery_offset_db (35640) + turnrestrictions (35640)
Change History (4)
by , 5 years ago
| Attachment: | JOSM-mess.tif added |
|---|
comment:1 by , 5 years ago
Forgot to mention, but I have used JOSM for quite a long time - the problems appeared after recent updates (JOSM / Java).
comment:2 by , 5 years ago
That's very likely not a JOSM problem. Recommendation would be to switch to a recent Java version, e.g. 16 or 11 (LTS).
comment:3 by , 5 years ago
| Description: | modified (diff) |
|---|



Screen shot of JOSM when the display is completely messed up.