Maxon Developers Maxon Developers
    • Documentation
      • Cinema 4D Python API
      • Cinema 4D C++ API
      • Cineware API
      • ZBrush Python API
      • ZBrush GoZ API
      • Code Examples on Github
    • Forum
    • Downloads
    • Support
      • Support Procedures
      • Registered Developer Program
      • Plugin IDs
      • Contact Us
    • Categories
      • Overview
      • News & Information
      • Cinema 4D SDK Support
      • Cineware SDK Support
      • ZBrush 4D SDK Support
      • Bugs
      • General Talk
    • Unread
    • Recent
    • Tags
    • Users
    • Login

    CallCommand() Undos

    SDK Help
    0
    2
    207
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • H
      Helper
      last edited by

      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.

      1 Reply Last reply Reply Quote 0
      • H
        Helper
        last edited by

        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

        1 Reply Last reply Reply Quote 0
        • First post
          Last post