Autoexpand validator report classes (Error, Warning, Other)

[mkoniecz]

What steps will reproduce the problem?

Currently at least my process for fixing validator issues is like this

0. Download area
1. Run validator
2. Get errors
3. Expand errors/warning group, whichever is the top one
4. Expand specific error/warning
5. Use right-click and select zoom to
6. Fix problem
7. Upload
8. Go back to 1.

What is the expected result?

What happens instead?

Point 3. (expanding the most severe problem group) happens automatically.

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

I think that vast majority of people fixes more important issues before less important so automatic opening error group will save significantly more time than waste.

URL:https://josm.openstreetmap.de/svn/trunk
Repository:UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b
Last:Changed Date: 2018-10-28 22:27:31 +0100 (Sun, 28 Oct 2018)
Build-Date:2018-10-28 21:33:32
Revision:14382
Relative:URL: ^/trunk

Identification: JOSM/1.5 (14382 en) Linux Ubuntu 16.04.5 LTS
Memory Usage: 953 MB / 953 MB (164 MB allocated, but free)
Java version: 1.8.0_191-b12, Oracle Corporation, Java HotSpot(TM) 64-Bit Server VM
Screen: :0.0 1920x1080
Maximum Screen Size: 1920x1080
Dataset consistency test: No problems found

Plugins:
+ OpeningHoursEditor (34535)
+ buildings_tools (34572)
+ continuosDownload (82)
+ imagery_offset_db (34641)
+ measurement (34529)
+ reverter (34552)
+ todo (30306)

Last errors/warnings:
- W: java.net.SocketTimeoutException: Read timed out
- W: java.net.SocketTimeoutException: Read timed out
- W: java.net.SocketTimeoutException: Read timed out
- W: java.net.SocketTimeoutException: Read timed out
- W: java.net.SocketTimeoutException: Read timed out
- W: java.net.SocketTimeoutException: Read timed out
- W: java.net.SocketTimeoutException: Read timed out
- E: org.openstreetmap.josm.io.OsmApiException: ResponseCode=400, Error Header=<You requested too many nodes (limit is 50000). Either request a smaller area, or use planet.osm>
- E: Bad Request - org.openstreetmap.josm.gui.widgets.HtmlPanel[,0,0,0x0,invalid,layout=java.awt.BorderLayout,alignmentX=0.0,alignmentY=0.0,border=,flags=9,maximumSize=,minimumSize=,preferredSize=]
- W: java.net.SocketTimeoutException: Read timed out

[skyper]

I'd prefer to remember the last state, as I do not unfold on purpose.

[GerdP]

This is also discussed in the German forum.
I see a potential problem with an automatic expansion as there is also code which tries to expand the last processed type of error. This is done when you autofix an error or use "Ignore for now". JOSM tries to focus on the next error.

Some dialog programs have right-click-menu options like "Unfold all", "Collapse all". Would that help here?

[MKnight]

cannot reproduce in 18360
the error list is empty after upload

[mkoniecz]

the check list is empty after upload

This report is about a different situation. See:

0. Download area
1. Run validator
2. Get errors
3. Expand errors/warning group, whichever is the top one

(...)

Point 3. (expanding the most severe problem group) happens automatically.

Some dialog programs have right-click-menu options like "Unfold all", "Collapse all". Would that help here?

Not really, I would still need to click on something.

[mkoniecz]

I'd prefer to remember the last state, as I do not unfold on purpose.

In such case how you use validator? Are you able to guess what is reported based on just what is highlighted with yellow/red?