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 IsSelected Example

    Bugs
    0
    5
    1.4k
    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

      THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

      On 18/03/2003 at 07:28, xxxxxxxx wrote:

      User Information:
      Cinema 4D Version:   8.012 
      Platform:   Windows  ;   
      Language(s) :     C++  ;

      ---------
      Not a bug, but a doc mistake:
      BaseSelect Class, IsSelected() variable example is:
      LONG seg=0,a,b,i;
        
        while (bs->GetRange(seg++,&a,&b)
        {
          for (i=a; i<=b)
          {
            // ... do something - i is the selected element
          }
        }

      But it should be this to work at all:
      LONG seg=0,a,b,i;
        
        while (bs->GetRange(seg++,&a,&b))
        {
          for (i=a; i<=b;i++)
          {
            // ... do something - i is the selected element
          }
        }
      Haven´t I already reported this some time ago?...

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

        THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

        On 18/03/2003 at 08:50, xxxxxxxx wrote:

        Maybe, it is a minor typing error in a rather large complex document, I'm sure it will be corrected, do you remember where you reported it?

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

          THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

          On 18/03/2003 at 08:59, xxxxxxxx wrote:

          where I reported it? Well, in a place we both have access too 😉
          yes it surely is a typing error but it still should be corrected 🙂

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

            THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

            On 23/05/2003 at 03:48, xxxxxxxx wrote:

            Sorry, this wasn't fixed in the third edition of the docs. But it is now fixed in the database for the next edition... 🙂

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

              THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

              On 23/05/2003 at 10:05, xxxxxxxx wrote:

              thanks 🙂

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