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]" Marco
_______________________________________________ User-friendly Desktop Internet GIS (uDig) http://udig.refractions.net http://lists.refractions.net/mailman/listinfo/udig-devel
