![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Affects Versions:
|
UDIG 1.3.2 |
|
Assignee:
|
Unassigned |
|
Components:
|
tools and editing |
|
Created:
|
12/Sep/12 7:33 AM
|
|
Description:
|
Commit tool uses a command queue to "cast" to Stores the command already > performed on layer features, but..
..what happens if a user performs some edits (or executes Split and Merge tools) then removes the layer, supposing so to discard any uncommitted change?
Well.. ..if he/she adds the same layer again (or even if he doesn't!), performs some other editing and then "Commits".. ..he has the WHOLE queue of commands executed, comprising those commands he/she didn't want!
Why can't we remove from command queue THOSE UNCOMMITTED COMMANDS related to a layer that is asked to be "Deleted" by the user.. ..eventually asking for:
"The layer under deletion has uncommitted changes: save them? [yes] [no][abort]"
|
|
Environment:
|
All platforms
|
|
Project:
|
uDIG
|
|
Priority:
|
![Minor]() Minor
|
|
Reporter:
|
Marco Foi
|
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
_______________________________________________
User-friendly Desktop Internet GIS (uDig)
http://udig.refractions.net
http://lists.refractions.net/mailman/listinfo/udig-devel
