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
    • Recent
    • Tags
    • Users
    • Register
    • Login

    Custom GUI

    Scheduled Pinned Locked Moved SDK Help
    2 Posts 0 Posters 203 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 14/08/2005 at 14:29, xxxxxxxx wrote:

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

      ---------
      Greetings:
      _OK, I have been reading the custom gui documentation and looking at the posts here. It seems that a custom datatype is required to get a custom gui working. Is this correct? Is there no way to create a general user area in the attributes manager without a custom datatype? Is there a complete example of a custom datatype and custom gui linked to work together? I found bits and pieces but nothing complete. Appreciate any help.

      Thank you,
      Damon_

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

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

        On 14/08/2005 at 15:29, xxxxxxxx wrote:

        There are a bunch of built-in custom gui's for the basic types (Bool, Real, LONG, Vector, Color, Texture, and so on). If this is all that you need, you can construct a static AM interface using "description resources". You can augment an AM interface with dynamic description resources using these same custom gui's as well (see MorphMixer.cpp GetDDescription() in the docs and SDK example source).

        You should only need a custom datatype with custom gui if you need to show data in the AM that is not covered by the available types or in the desired graphical way.

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