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

    Tool Data and Gedialog

    Scheduled Pinned Locked Moved SDK Help
    5 Posts 0 Posters 431 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 23/09/2009 at 03:29, xxxxxxxx wrote:

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

      ---------
      Hello All,
      I have some DescriptionToolData and one GeDialog and i'dd like to control Parameter and command of tool with my Dialog and not via AM, but i can't find the way to connect tool with Dialog.
      Any Help?
      Thanks in advance
      Franz

      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 24/09/2009 at 05:14, xxxxxxxx wrote:

        Hello..... any help ??
        Franz

        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 24/09/2009 at 08:36, xxxxxxxx wrote:

          Tool plugins can utilize a SubDialog which is used in the A.M. instead of direct Description resources. In order to use a GeDialog, you'd need to set up the description resources in the ToolData but hide them. Then pipe the dialog settings to their counterpart descriptions so that interactive value changes are handled properly (creation of undos, calls to SetDParameter, Draw, etc.).

          Piping them is your problem, of course. You can establish a 'connection' to your dialog from your tool plugins in two ways:

          1. Using messages: you could use MultiMessage (might be slow) to disperse the message that will only be handled by your plugins looking for the message.

          2. Direct setting/getting: Have the tool create the dialog (with unique ID!) if nonexistent and have others point to it. Then each can call methods (or access public variables) of the dialog.

          Are you wanting to create a single GeDialog for all instances and types of your DescriptionToolData or one per? This will make a difference.

          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 24/09/2009 at 08:59, xxxxxxxx wrote:

            Hello Robert,
            Thanks for you reply 🙂
            i need to create a single interface for my n tool, in particualr i have some modeling tools and my gedialog is a input interface for some tool  common parameters.
            i saw now GetToolData with this i meaby can set tool container value from dialog, i am right ?

            all the best
            franz

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

              That would be a good way to populate the dialog with the tool parameters and set them (via the BaseContainer retrieved) as the user interacts with the dialog elements. In this way, you won't need to keep a pointer to the dialog in the tool data class but can simply get the tool container as needed to set/get values. Be careful with data not stored in the BaseContainer such as any arrays you have as class members in your ToolData class. As long as the dialog doesn't need to reference them, you should be in good shape.

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