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

    FreeTool expects None not Bool

    Scheduled Pinned Locked Moved Bugs
    2 Posts 0 Posters 578 Views
    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 Offline
      Helper
      last edited by

      On 29/06/2016 at 15:45, xxxxxxxx wrote:

      User Information:
      Cinema 4D Version:   17 
      Platform:      
      Language(s) :

      ---------
      The c4d.plugins.ToolData.FreeTool() method documentation says it should return a Bool, however when I return a Bool I get this error:

      "TypeError: FreeTool expected None, not bool"

        
      class SphereTool(plugins.ToolData) :   
          """Inherit from ToolData to create your own tool"""   
        
        
          def InitTool(self, doc, data, bt) :   
              """Called each time the tool is selected.   
              :return: True if there was no error, otherwise False.   
              """   
              return True   
        
          def FreeTool(self, doc, data) :   
              """Called each time the user chooses another tool.   
              :return: True if there was no error, otherwise False.   
              """   
              return True   
      
      1 Reply Last reply Reply Quote 0
      • H Offline
        Helper
        last edited by

        On 30/06/2016 at 02:37, xxxxxxxx wrote:

        Hi Donovan,

        this is a known bug in the documentation, it is already fixed. The fix will be published with the next update.
        Nevertheless thanks for taking the time to report it.

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