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
    • Login

    Enable box in expression plugin tag

    Scheduled Pinned Locked Moved SDK Help
    2 Posts 0 Posters 199 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 10/11/2009 at 18:04, xxxxxxxx wrote:

      User Information:
      Cinema 4D Version:   11.027 
      Platform:      Mac OSX  ; 
      Language(s) :   C.O.F.F.E.E  ;

      ---------
      I've created a couple different expression plugin tags. I want the user to be able to disable them the way they are used to with most native expression tags. It might be nice to allow them to change the priority as well:

      Is there a way to provide these standard "Basic Properties" elements? I suppose I could create a user data boolean for the expression tag and test for its state, but that seems clumsy if such an option is built-in to the expression tag SDK.
      Thanks,
      G

      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 17/11/2009 at 05:17, xxxxxxxx wrote:

        Unfortunatly the standard expression interface is not supported in COFFEE.

        cheers,
        Matthias

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