Error report after using 'q' to orthogonalise a 'building' which has been terraced

[nick-tallguy]

What steps will reproduce the problem?

1. create a buiding using building tool
2. terrace the building into 2 semi's
3. add an entension to the building & press 'q' to make it square

What is the expected result? orthogonallised shape

What happens instead? - error message

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

Repository Root: http://josm.openstreetmap.de/svn
Build-Date: 2011-09-05 01:31:49
Last Changed Author: bastiK
Revision: 4399
Repository UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b
URL: http://josm.openstreetmap.de/svn/trunk
Last Changed Date: 2011-09-04 22:13:51 +0200 (Sun, 04 Sep 2011)
Last Changed Rev: 4399

Identification: JOSM/1.5 (4399 en_GB)
Memory Usage: 72 MB / 757 MB (8 MB allocated, but free)
Java version: 1.6.0_22, Sun Microsystems Inc., OpenJDK Server VM
Operating system: Linux
Dataset consistency test: No problems found

Plugin: FixAddresses (26606)
Plugin: ImproveWayAccuracy (26610)
Plugin: OpeningHoursEditor (26606)
Plugin: buildings_tools (26606)
Plugin: download_along (26606)
Plugin: gpxfilter (26606)
Plugin: imageryadjust (26606)
Plugin: mapdust (26606)
Plugin: measurement (26606)
Plugin: openstreetbugs (26606)
Plugin: terracer (26606)
Plugin: turnlanes (26606)
Plugin: turnrestrictions (26606)

java.lang.NullPointerException
	at org.openstreetmap.josm.actions.mapmode.SelectAction.getCursor(SelectAction.java:219)
	at org.openstreetmap.josm.actions.mapmode.SelectAction.mouseDragged(SelectAction.java:363)
	at java.awt.AWTEventMulticaster.mouseDragged(AWTEventMulticaster.java:320)
	at java.awt.Component.processMouseMotionEvent(Component.java:6316)
	at javax.swing.JComponent.processMouseMotionEvent(JComponent.java:3285)
	at java.awt.Component.processEvent(Component.java:6037)
	at java.awt.Container.processEvent(Container.java:2045)
	at java.awt.Component.dispatchEventImpl(Component.java:4629)
	at java.awt.Container.dispatchEventImpl(Container.java:2103)
	at java.awt.Component.dispatchEvent(Component.java:4455)
	at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4633)
	at java.awt.LightweightDispatcher.processMouseEvent(Container.java:4314)
	at java.awt.LightweightDispatcher.dispatchEvent(Container.java:4227)
	at java.awt.Container.dispatchEventImpl(Container.java:2089)
	at java.awt.Window.dispatchEventImpl(Window.java:2517)
	at java.awt.Component.dispatchEvent(Component.java:4455)
	at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:649)
	at java.awt.EventQueue.access$000(EventQueue.java:96)
	at java.awt.EventQueue$1.run(EventQueue.java:608)
	at java.awt.EventQueue$1.run(EventQueue.java:606)
	at java.security.AccessController.doPrivileged(Native Method)
	at java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:105)
	at java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:116)
	at java.awt.EventQueue$2.run(EventQueue.java:622)
	at java.awt.EventQueue$2.run(EventQueue.java:620)
	at java.security.AccessController.doPrivileged(Native Method)
	at java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:105)
	at java.awt.EventQueue.dispatchEvent(EventQueue.java:619)
	at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:275)
	at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:200)
	at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:190)
	at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:185)
	at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:177)
	at java.awt.EventDispatchThread.run(EventDispatchThread.java:138)

[bastiK]

Reproducible?

Looks like a problem in the MapMode code.

[xeen]

I can't reproduce the issue (probably there is some condition, which needs to be true as well). However, the stacktrace is clear enough and it can be easily fixed. I'll commit a patch in a minute and mark this issue fixed, please verify it doesn't occur with the new JOSM version. If it does, please reopen this ticket.

[xeen]

In [4412/josm]:

probably fix #6806