Opened 13 years ago
Closed 13 years ago
#7861 closed defect (wontfix)
remote control: set default to download to new layer
| Reported by: | skyper | Owned by: | framm |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Core remotecontrol | Version: | latest |
| Keywords: | remote control default new layer | Cc: |
Description (last modified by )
Attachments (0)
Change History (6)
comment:1 by , 13 years ago
| Description: | modified (diff) |
|---|
follow-up: 4 comment:2 by , 13 years ago
comment:3 by , 13 years ago
There is Download objects to new layer setting under Preferences/Remote control which seems to do exactly that.
comment:4 by , 13 years ago
Replying to simon04:
I disagree. Not downloading to a new layer has been in use for several years now. The undo-ability exists for a few months. Therefore, I'd stick with the old beaviour.
No, undo has, as far as I know, never worked. It seems to be a bigger problem. I would prefer to get undo working but, sorry, I do not see it happen quite soon. Please surprise me.
Think of a new user trying to fix some bugs using the remote control feature and having to deal with 20 open layers at some point …
I remember some time ago, propably before core integration, you were always ask about opening a new layer or not.
comment:5 by , 13 years ago
I disagree too, this change would upset a lot of people. Especially when using QA tools such as Osmose in France, it is highly appreciated to download only erroneous primitives, one by one, during a QA mapping session. Creating a new layer for each primitive would be terribly annoying.
comment:6 by , 13 years ago
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |



I disagree. Not downloading to a new layer has been in use for several years now. The undo-ability exists for a few months. Therefore, I'd stick with the old beaviour.
Think of a new user trying to fix some bugs using the remote control feature and having to deal with 20 open layers at some point …