CAESAR offers a number of node number management tools summed up as "block tools."

I submit that it would benefit the user to pop up a confirmation dialogue each time before a block operation commences, in the event the user inadvertently selects an incorrect block operation.

Sometimes node number inversion turns the system into space dust when the user selects "undo," losing work.

Thanks.

Michael,

Can you provide a model and a workflow so we can see where the "undo" falls apart. I'd like to get this fixed.

Richard,

Unfortunately, the problem is verified random.

Start with file A. Copy to A-copy. Make 1 complicated change (e.g. inversion that covers a range of non-contiguous regions, nodes, cnodes, etc.) Undo, and certain carry-forward parameters aren't handled correctly, as well as nodes/cnodes.

Close the file without saving and repeat. No problem.

Delete A-copy and recreate A-copy from A. Still no problem.

Maybe it's a reserved RAM space problem, but I'm out of my element here.

Here is one bug that seems similar (but not specifically related to undo).

Start with a file with wind enabled on the first element and only the first element.

Select any contiguous number of elements in the elements tab. Right click and select change sequence, and then follow.

Double click on a graphical element. Look in the wind/wave tab. See screenshot.

We will look into each of these issues.