#17469 closed enhancement (fixed)
Validator: add shortcut to zoom/move to next issue
Reported by: | bagage | Owned by: | team |
---|---|---|---|
Priority: | normal | Milestone: | 19.03 |
Component: | Core | Version: | |
Keywords: | template_report | Cc: | Don-vip |
Description
What's the use case?
When I run validator, I try to fix all errors/warnings that were triggered. Currently it's a bit cumbersome because:
- you have to open all categories one by one (not for long though #17295 :)), then double click on an issue to zoom on it.
- solve the issue
- repeat step 1-2 until you have treated all issues
I personally modified my workflow as follow:
- select all errors in the list
- then use button "select" which selects items on the map
- then I add them in todo plugin
- double click first item in the todolist
- fix it
- use todo plugin feature "mark as done". It then automatically selects next item and zoom on it.
It's much better IMHO. But maybe this behavior could be implemented directly in the validation list, eg:
- Have a shortcut to zoom on first error/warning
- Have another shortcut to mark the current error/warning as treated (or skipped). This would automatically moves to next item. Maybe items considered as treated could have a checkmark or similar to see what items are left to treat?
An alternative would be somehow a shortcut to fill the todo plugin list directly from the validator?
Please provide any additional information below. Attach a screenshot if possible.
Build-Date:2019-03-16 11:06:26 Revision:14887 Is-Local-Build:true Identification: JOSM/1.5 (14887 SVN fr) Linux Debian GNU/Linux buster/sid Memory Usage: 1645 MB / 4436 MB (1228 MB allocated, but free) Java version: 1.8.0_191-8u191-b12-2-b12, Oracle Corporation, OpenJDK 64-Bit Server VM Screen: :0.0 1920x1080 Maximum Screen Size: 1920x1080 Java package: openjdk-8-jre:amd64-8u191-b12-2 Java ATK Wrapper package: libatk-wrapper-java:all-0.33.3-21 Dataset consistency test: No problems found Plugins: + AddrInterpolation (34867) + HouseNumberTaggingTool (34867) + OpeningHoursEditor (34867) + PicLayer (34867) + buildings_tools (34904) + conflation (0.6.2) + jts (34524) + poly (34867) + scripting (30794) + terracer (34867) + todo (30306) + utilsplugin2 (34915) Last errors/warnings: - W: No configuration settings found. Using hardcoded default values for all pools. - W: Cannot start IPv4 remotecontrol https server on port 8112: Keystore was tampered with, or password was incorrect - W: Cannot start IPv6 remotecontrol https server on port 8112: Keystore was tampered with, or password was incorrect - E: org.openstreetmap.josm.io.OsmApiException: ResponseCode=500 - W: org.openstreetmap.josm.io.OsmApiException: ResponseCode=500 - W: org.openstreetmap.josm.io.OsmApiException: ResponseCode=500 - W: Region [WMS_BLOCK_v2] Resetting cache - W: Region [WMTS_BLOCK_v2] Resetting cache
Attachments (1)
Change History (12)
comment:1 by , 6 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
comment:2 by , 6 years ago
Please reopen this ticket if this simple solution doesn't solve the problem.
comment:4 by , 6 years ago
Thanks GerdP for the quick patch! It seems that this action is not key bindable though, is it? Same for "Zoom on issue". If both were bindable I think this solution would be totally ideal!
comment:5 by , 6 years ago
The "Zoom to problem" action is already bound to key "6".
It is quite difficult to find new key bindings because most are already in use, see
https://josm.openstreetmap.de/wiki/DevelopersGuide/ShortcutsList
comment:6 by , 6 years ago
Indeed there are already a bunch of shortcuts. But isn't it possible to make it bindable, with no default binding? I'd happily remove another personally for that.
by , 6 years ago
Attachment: | 17469-shortcut.patch added |
---|
Allow to bind shortcut to "Ignore for now" action
comment:7 by , 6 years ago
Cc: | added |
---|---|
Resolution: | fixed |
Status: | closed → reopened |
I think you have to have the validator panel open before you can change the shortcut. For me it is changed to Ctrl+Alt+F2.
@Vincent I'd prefer to enable/disable the command depending on the context but I didn't find out how. Please let me know if you think this patch can cause problems.
comment:9 by , 6 years ago
Resolution: | → fixed |
---|---|
Status: | reopened → closed |
I think Shift+Minus is quite intuitve for a "remove action" and it wasn't in use.
comment:10 by , 6 years ago
Milestone: | → 19.03 |
---|
In 14889/josm: