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

    Tag-Plugin with Attributes

    Scheduled Pinned Locked Moved SDK Help
    3 Posts 0 Posters 267 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 08/02/2006 at 08:00, xxxxxxxx wrote:

      User Information:
      Cinema 4D Version:   R9.5 
      Platform:   Windows  ;   
      Language(s) :   C.O.F.F.E.E  ;

      ---------
      Hello all Coders 🙂
      I can do a Tag-Plugin and I can do a Menuplugin.
      But I don't know how can I do a Attributemenu for the Tag-Plugin.
      Please Help me...

      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 08/02/2006 at 13:23, xxxxxxxx wrote:

        Do you mean information in the Attribute Manager?

        This is done in two ways:

        1. Statically: by defining the .res, .str, and .h files that define the Descriptions for the Tag. Say you have a TagPlugin given Tmytag, then you need a Tmytag.h, Tmytag.res, and Tmytag.str, the latter go into the 'res/description' and 'res/strings_XX/description' folders, respectively.

        2. Dynamically: by creating description types and adding to the description. In C++, this is accomplished with GetDDescription(). No idea about COFFEE.

        If you only need static description resources, you just create a header with an enum for the .res elements. See "Description Resource" in the C++ SDK Docs for information on what is in the .res file (very similar to Dialog resources, but not identical). The .str file contains strings for your description elements, basically text for buttons, boxes, groups, etc.

        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 09/02/2006 at 06:45, xxxxxxxx wrote:

          Thanks for replay 🙂
          I need only a static menu.
          It sounds like a Tag has a Layout like a Menu-Plugin.
          The Menu-Plugin call Layout for define the Attributes of the Menu, optional I can use .res for describe Attributes.
           
          Is it the same in Coffee ?
           
          PS: I get first Steps in C++ with Visual C++ Express and hope, that I can do it in C++ in few days. Hope ! But I get start trouble ...

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