Modify ↓
#17432 closed defect (fixed)
Unexpected exception adding point by coordinates
Reported by: | Silva1989 | Owned by: | team |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | Plugin utilsplugin2 | Version: | |
Keywords: | template_report | Cc: | emanuelfreitassilva@… |
Description
What steps will reproduce the problem?
- More Tools, selecting Add point by coordinates
- The requested window opens, the coordinate introduction box doesn't show
- Clicking okay, the unexpected exception shows up
What is the expected result?
What happens instead?
Please provide any additional information below. Attach a screenshot if possible.
URL:https://josm.openstreetmap.de/svn/trunk Repository:UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b Last:Changed Date: 2019-03-03 00:16:03 +0100 (Sun, 03 Mar 2019) Build-Date:2019-03-02 23:16:53 Revision:14824 Relative:URL: ^/trunk Identification: JOSM/1.5 (14824 pt) Windows 10 64-Bit OS Build number: Windows 10 Enterprise 1903 (18351) Memory Usage: 234 MB / 1339 MB (52 MB allocated, but free) Java version: 1.8.0_201-b09, Oracle Corporation, Java HotSpot(TM) Client VM Screen: \Display0 1920x1080, \Display1 1920x1080 Maximum Screen Size: 1920x1080 Dataset consistency test: No problems found Plugins: + apache-commons (34506) + continuosDownload (82) + ejml (34389) + geotools (34513) + jaxb (34678) + jts (34524) + opendata (34899) + utilsplugin2 (34867) Last errors/warnings: - W: Unable to request certificate of https://grca.nat.gov.tw - W: Not a single layer for the name 'SRIT FAI54': [] - W: Not a single layer for the name 'SRIT FAI56': [] - W: Not a single layer for the name 'SRIT FAI57': [] - W: Not a single layer for the name 'SRIT FAI55': [] - W: Not a single layer for the name 'SRIT FAI58': [] - W: No configuration settings found. Using hardcoded default values for all pools. - E: Handled by bug report queue: java.util.NoSuchElementException === REPORTED CRASH DATA === BugReportExceptionHandler#handleException: No data collected. Warning issued by: BugReportExceptionHandler#handleException === STACK TRACE === Thread: AWT-EventQueue-0 (15) of main java.util.NoSuchElementException at java.util.LinkedList$ListItr.next(Unknown Source) at org.openstreetmap.josm.command.SequenceCommand.<init>(SequenceCommand.java:56) at org.openstreetmap.josm.command.SequenceCommand.<init>(SequenceCommand.java:65) at org.openstreetmap.josm.plugins.utilsplugin2.latlon.LatLonAction.actionPerformed(LatLonAction.java:85) at javax.swing.AbstractButton.fireActionPerformed(Unknown Source) at javax.swing.AbstractButton$Handler.actionPerformed(Unknown Source) at javax.swing.DefaultButtonModel.fireActionPerformed(Unknown Source) at javax.swing.DefaultButtonModel.setPressed(Unknown Source) at javax.swing.AbstractButton.doClick(Unknown Source) at javax.swing.plaf.basic.BasicMenuItemUI.doClick(Unknown Source) at javax.swing.plaf.basic.BasicMenuItemUI$Handler.mouseReleased(Unknown Source) at java.awt.AWTEventMulticaster.mouseReleased(Unknown Source) at java.awt.Component.processMouseEvent(Unknown Source) at javax.swing.JComponent.processMouseEvent(Unknown Source) at java.awt.Component.processEvent(Unknown Source) at java.awt.Container.processEvent(Unknown Source) at java.awt.Component.dispatchEventImpl(Unknown Source) at java.awt.Container.dispatchEventImpl(Unknown Source) at java.awt.Component.dispatchEvent(Unknown Source) at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source) at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source) at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source) at java.awt.Container.dispatchEventImpl(Unknown Source) at java.awt.Window.dispatchEventImpl(Unknown Source) at java.awt.Component.dispatchEvent(Unknown Source) at java.awt.EventQueue.dispatchEventImpl(Unknown Source) at java.awt.EventQueue.access$500(Unknown Source) at java.awt.EventQueue$3.run(Unknown Source) at java.awt.EventQueue$3.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(Unknown Source) at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(Unknown Source) at java.awt.EventQueue$4.run(Unknown Source) at java.awt.EventQueue$4.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(Unknown Source) at java.awt.EventQueue.dispatchEvent(Unknown Source) at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source) at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source) at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source) at java.awt.EventDispatchThread.pumpEvents(Unknown Source) at java.awt.EventDispatchThread.pumpEvents(Unknown Source) at java.awt.EventDispatchThread.run(Unknown Source)
Attachments (0)
Change History (4)
comment:1 by , 6 years ago
comment:2 by , 6 years ago
Component: | Core → Plugin utilsplugin2 |
---|
comment:4 by , 6 years ago
I've noticed that the core action Shift+D doesn't show this problem. I wonder why we maintain both versions of LatLonDialog?
Note:
See TracTickets
for help on using tickets.
I can reproduce this when I use the mouse to shrink the size of the dialog so that the input field is not shown and pressing Cancel. Next time when I use LatLon Tool (Shift+Ctrl+L) the dialog opens with the last used size and one has to enlarge the dialog again so that the input field is shown.