 |
>> "That is, the move and the dupe would be undone" No, this is not the planned behaviour. If you move a brush this is an action in itself. Why should DarkRadiant undo subsequent changes after cloning - and where should it stop? When first reading this report, I thought you were reporting a failure that prevents cloned stuff from being removed when undo is hit, but this is working as intended: - Create a brush - Clone it - Hit Ctrl-Z - The clone is gone (whether Offset is active or not) |
 |
I do agree; it shouldn't do more than one step at a time. I made a suggestion in the "two most annoying" thread about seeking dupes. Maybe that would take care of all such problems, if it's easy enough. |
- Anonymous
