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

    Not a bug - a suggestion for MinMax

    Scheduled Pinned Locked Moved Bugs
    1 Posts 0 Posters 393 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

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

      On 22/03/2006 at 13:55, xxxxxxxx wrote:

      User Information:
      Cinema 4D Version:   9.521 
      Platform:   Windows  ;   
      Language(s) :   C.O.F.F.E.E  ;  C++  ;  XPRESSO  ;

      ---------
      I noticed that the MinMax class uses a "used" member variable to track whether the min and max members have been initialized or not. It might be more efficient, in the "init" routine, to just set the min to its max value, and the max to its min value. That way, you can
       
      1. Get rid of the member variable
      2. Get rid of the conditional code in the AddPoint() routine
       
      Just a thought - probably not in the "critical path" for performance, but I thought I'd mention it.
       
      Brian C. Barnes
      Senior Member, Technical Staff
      Advanced Micro Devices

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