Well there is always the cya "are you sure you want to delete" idiot pop up button.
For the actual undo, you could do something similar to copy and "stack" it. I am not sure what mechanism is used for the copy but the undo could work in the same way. Also, would it only undo elements on the graph or property and state changes? Sent from my iPhone > On Aug 8, 2015, at 12:01 AM, Joe Witt <[email protected]> wrote: > > The motive here is prevention from unintended modification. > > Undo, as part of a larger versioning effort, is a good step as well. > >> On Fri, Aug 7, 2015 at 11:44 PM, Adam Taft <[email protected]> wrote: >> Alternative suggestion: undo >> >> It shouldn't be too hard to keep multiple diffs of the flow.xml around to >> allow for some sort of undo capabilities. What are the thoughts or >> concerns for supporting undo? >> >>> On Fri, Aug 7, 2015 at 10:31 PM, Joe Witt <[email protected]> wrote: >>> >>> Team, >>> >>> We've been hearing from users of nifi that it is too easy to >>> accidentally move something on the flow or delete large portions of >>> the flow. This is the case when panning the screen for example and >>> accidentally having a processor selected instead. >>> >>> What is worth consideration then is the notion of making the flow >>> 'read-only' by default. In this case the user would need to >>> explicitly 'enable edit mode'. We would then also support a >>> confirmation dialog or similar construct whenever deleting components >>> on the flow. >>> >>> Anyone have a strong objection to this concept? If so, do you have an >>> alternative in mind that would help avoid accidental movement? >>> >>> Thanks >>> Joe >>>
