Modify

Opened 4 years ago

Last modified 8 months ago

#18921 new defect

Minimum height of dialog field to avoid endless flickering

Reported by: Hb--- Owned by: team
Priority: trivial Milestone:
Component: Core imagery Version:
Keywords: template_report java8 windows classic laf Cc:

Description

What steps will reproduce the problem?

  1. Copy https://tiles0.planet.com/basemaps/v1/planet-tiles/australia_wildfire_weekly_visual_2020-01-20_to_2020-01-27_mosaic/gmap/{zoom}/{x}/{y}.png?api_key=ExampleForLongURLText
  2. Open the Imagery preferences.
  3. Click TMS, the Add Imagery URL dialog opens as shown in the screenshot.
  4. Paste the long URL into the first field

What is the expected result?

That the pasted long URL is accepted.

What happens instead?

The from field takes the whole size of the dialog box.
The text flickers endlessly like being reformatted.
Can't enter a name for the imagery and can't click OK.

Please provide any additional information below. Attach a screenshot if possible.

Error happens only under Java 8 for long texts when the initial height of the field is smaller than the usual font size in the dialog.

  1. For a first solution, please make this whole dialog wider.
  1. Why does Java/JOSM present text input fields which are taller than the font?

Java 13 seems to format the whole dailog box different and present bigger text fields.

Initial dialog size:

Flickering field:

Attached screenshots are reduced by 50% in size.

URL:https://josm.openstreetmap.de/svn/trunk
Repository:UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b
Last:Changed Date: 2020-03-10 23:31:54 +0100 (Tue, 10 Mar 2020)
Build-Date:2020-03-11 02:30:52
Revision:16111
Relative:URL: ^/trunk

Identification: JOSM/1.5 (16111 en) Windows 7 64-Bit
OS Build number: Windows 7 Professional (7601)
Memory Usage: 1818 MB / 3604 MB (109 MB allocated, but free)
Java version: 1.8.0_242-b08, AdoptOpenJDK, OpenJDK 64-Bit Server VM
Screen: \Display0 1280x1024
Maximum Screen Size: 1280x1024
VM arguments: [-Djosm.home=jtest]
Program arguments: [--language=en]
Dataset consistency test: No problems found

Plugins:
+ buildings_tools (35248)
+ utilsplugin2 (35334)

Attachments (3)

scrInitialSize.png (118.8 KB ) - added by Hb--- 4 years ago.
scrFlickering.png (105.5 KB ) - added by Hb--- 4 years ago.
scrJOSMLook&Feel=WindowsClassic.png (62.2 KB ) - added by Hb--- 4 years ago.

Download all attachments as: .zip

Change History (8)

by Hb---, 4 years ago

Attachment: scrInitialSize.png added

by Hb---, 4 years ago

Attachment: scrFlickering.png added

comment:1 by skyper, 4 years ago

Component: CoreCore imagery

comment:2 by Don-vip, 4 years ago

Keywords: windows added
Owner: changed from team to Hb---
Status: newneedinfo

Can you please try with the "Windows" look-and-feel instead of "Windows Classic"?

in reply to:  2 comment:3 by Hb---, 4 years ago

Owner: changed from Hb--- to team
Status: needinfonew

Replying to Don-vip:
I do use a "Classic" theme for the complete OS. So the initial report was already based on the JOSM look&feel "Windows".

Switching the JOSM look&feel to Windows Classic gives the result of a non flickering first field. The bug is therefore not present.

But the Name field is still not accessible, see screenshot. It becomes visible when the dialog size is increased by dragging its border.

comment:4 by gaben, 9 months ago

Keywords: classic laf added

comment:5 by gaben, 8 months ago

@Hb--- Is is still reproducible with any recent Java version?

Modify Ticket

Change Properties
Set your email in Preferences
Action
as new The owner will remain team.
as The resolution will be set. Next status will be 'closed'.
to The owner will be changed from team to the specified user.
Next status will be 'needinfo'. The owner will be changed from team to Hb---.
as duplicate The resolution will be set to duplicate. Next status will be 'closed'. The specified ticket will be cross-referenced with this ticket.
The owner will be changed from team to anonymous. Next status will be 'assigned'.

Add Comment


E-mail address and name can be saved in the Preferences .
 
Note: See TracTickets for help on using tickets.