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

    SDK wrong type NodeData.CopyTo

    Scheduled Pinned Locked Moved Bugs
    2 Posts 0 Posters 562 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 17/04/2017 at 05:00, xxxxxxxx wrote:

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

      ---------
      https://developers.maxon.net/docs/py/2023_2/modules/c4d.plugins/BaseData/NodeData/index.html#NodeData.CopyTo
      Dnode is actually a GeListNode and not a NodeData as said in the sdk and in the C++ sdk.
      Which is the contradiction with what is writtent:
      Actually dnode == dest. It's not true.
      It make a huge change since that mean dnode is the instance of node(which is on the scene) while dest is the instance of our class.

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

        On 17/04/2017 at 08:52, xxxxxxxx wrote:

        Hi,

        I confirm the Python SDK docs are wrong for NodeData.CopyTo().
        dest is the plugin's  NodeData instance while dnode is its GeListNode representation.
        So these objects are not equal but they have a strong relation.

        The docs for NodeData.CopyTo() will be fixed. Thanks for reporting.

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