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

    VPBuffer::GetLine() 32 Bit Docs

    Scheduled Pinned Locked Moved Bugs
    3 Posts 0 Posters 684 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 30/04/2015 at 15:43, xxxxxxxx wrote:

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

      ---------
      The documentation says that if the line should be retrieved with a bitdepth of 32, the datatype
      should be Float. Shouldn't it be Float32? Since Float  could also be Float64.

      https://developers.maxon.net/docs/cpp/2023_2/class_v\_p_buffer.html#aa4719c25589d79056350a82703f144dc

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

        On 04/05/2015 at 16:34, xxxxxxxx wrote:

        Hi NiklasR,

        We've carefully checked, and can confirm that you're right.  For the 32 bit depth choice, it should always be Float32, never Float64, as the code is unconditionally compiled with Float32 and assumes such in its pointer arithmetic.

        Nice catch!  The documentation will be updated accordingly.

        Joey Gaspe
        SDK Support Engineer

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

          On 19/01/2016 at 06:05, xxxxxxxx wrote:

          The documentation hasn't been updated yet and I fell for it just another time. :clown:

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