Imagery layer offset not saved

[pinkduck]

What steps will reproduce the problem?

1. Add imagery layer
2. menu Imagery > New Offset
3. Drag to move layer offset
4. Click OK button in offset dialog
5. Drag again on imagery layer

What is the expected result?

Layer remains in place once dialog accepted

What happens instead?

The layer continues to be moved until Enter key is pressed

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

Relative:URL: ^/trunk
Repository:UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b
Last:Changed Date: 2018-03-26 22:16:39 +0200 (Mon, 26 Mar 2018)
Revision:13576
Redirecting:to URL 'https://josm.openstreetmap.de/svn/trunk':
Build-Date:2018-03-26 20:45:23
URL:https://josm.openstreetmap.de/svn/trunk

Identification: JOSM/1.5 (13576 en_GB) Windows 10 64-Bit
OS Build number: Windows 10 Pro 1709 (16299)
Memory Usage: 256 MB / 2048 MB (101 MB allocated, but free)
Java version: 9.0.4+11, Oracle Corporation, Java HotSpot(TM) 64-Bit Server VM
Screen: \Display0 1280x1024, \Display1 1280x1024
Maximum Screen Size: 1280x1024
VM arguments: [-XX:HeapDumpPath=JOSM.hprof, -Djava.net.useSystemProxies=true]
Dataset consistency test: No problems found

Plugins:
+ measurement (34109)
+ reverter (34109)
+ terracer (34109)
+ utilsplugin2 (34109)

Tagging presets:
+ C:\Users\Pink Duck\Downloads\JOSM Custom Presets.xml
+ https://josm.openstreetmap.de/josmfile?page=Presets/EnglandWalesRightsOfWay&zip=1

Map paint styles:
- https://josm.openstreetmap.de/josmfile?page=Styles/ParkingLanes&style&zip=1
- https://josm.openstreetmap.de/josmfile?page=Styles/Sidewalks&style&zip=1
- https://github.com/bastik/mapcss-tools/raw/osm/mapnik2mapcss/osm-results/mapnik.zip

Last errors/warnings:
- E: java.util.concurrent.ExecutionException: [powershell, -Command, [Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12;[System.Net.WebRequest]::Create('https://www.certigna.fr').GetResponse()]
- E: Failed to locate image 'styles/standard/vehicle/restriction/speed.png'
- W:  NSL: Could not get presets icon styles/standard/vehicle/restriction/speed.png
- W: No configuration settings found.  Using hardcoded default values for all pools.

[Adam Schneider]

This is happening for me too, using version 13576 on Mac OS X... except that pressing the Enter key does NOT clear it up; I have to restart JOSM to regain normal mouse control.

Reverting to JOSM 13500 doesn't seem to help, so maybe the problem is in an updated plugin?

[Don-vip]

Follow-up of #15716, #15849, #16053... I can't get this feature to work properly in all use cases...

[Klumbumbus]

Ticket #16151 has been marked as a duplicate of this ticket.

[Klumbumbus]

from #16151:

Last version that DOES NOT have this bug is 13533. Stable 13576 is buggy as well.

[Don-vip]

Ticket #16153 has been marked as a duplicate of this ticket.

[Don-vip]

Ticket #16179 has been marked as a duplicate of this ticket.

[Klumbumbus]

The video in #16179 show a bit different behavior. The align window disappears so clicking on OK is not possible at the beginning.

[Klumbumbus]

Ticket #16218 has been marked as a duplicate of this ticket.

[Don-vip]

In 13686/josm:

fix #16133, see #16053 - fix imagery layer offset bug (regression of r13546)

[Klumbumbus]

I just tested it in v13690 and it is still not fully fixed.

1. open dialog
2. press ESC
3. dialog closes
4. drag with left mouse button hold moves the background

[Don-vip]

In 13694/josm:

fix #16133, see #16053 - fix imagery layer offset bug (regression of r13546)

[ralph.a.aytoun@…]

I am also experiencing this problem on my Acer laptop on Windows 10 and JOSM version 13576. Pressing the "Enter" key does not free the imagery layer so cannot do any mapping.

I have found a work-around.

In the layers panel on the right I manually move the green "active layer" icon to the imagery layer that I want to move, then moving the imagery and pressing "OK", then manually moving the "active layer" icon back to the Data layer. This process allows JOSM to accept the moved imagery and revert back to mapping mode.

[Klumbumbus]

It should be fixed now since v13694. You can try the latest version or wait for the next stable version, which will be released soon.