Your browser does not seem to support JavaScript. As a result, your viewing experience will be diminished, and you have been placed in read-only mode.
Please download a browser that supports JavaScript, or enable it if it's disabled (i.e. NoScript).
On 08/04/2013 at 12:48, xxxxxxxx wrote:
User Information: Cinema 4D Version: Platform: Language(s) :
--------- Is there still no way to prevent a CallCommand() to create a new undo step? It is a huge limitation IMHO. Two small methods, like BaseDocument::BeginIgnoreStartUndo() and BaseDocument::EndIgnoreStartUndo() would be more than enough to ease the pain.
On 08/04/2013 at 13:58, xxxxxxxx wrote:
I agree. CallCommands() are the easiest way for beginners to get started coding. But due the way the Undos work. They are often not an option.
A long time ago I talked about this rather annoying problem with CallCommands() with some people. Including PerAnders(AKA Mr. Mograph). He suggested that Maxon might be able to create a switch that would let us turn off the internal UNDO's that are built into them.
-ScottA