>> delete_tagged() makes a deletion object for the undo mechanism. >> This object always contains one element. If delete_tagged() deletes many >> elements, it creates multiple delete objects -- one per element. >> >> Wouldn't it make more sense to move *all* deleted elements first into the >> deletion object, and only then register it for undo? That way delete_tagged() >> would only register a single undo action, etc. >> >> Or is the XCF_Delete code in the guts of undo unable to cope with multiple >> elements in the undo object?? > > No, it looks like something I coded up quickly and didn't notice that > it was done inefficiently. Just the sort of thing I find and correct > in other people's code. . .
;) Perfect, thank you -- Kuba _______________________________________________ Xcircuit-dev mailing list [email protected] http://www.opencircuitdesign.com/mailman/listinfo/xcircuit-dev
