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

    hiding res params in xpresso

    Scheduled Pinned Locked Moved SDK Help
    9 Posts 0 Posters 716 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/10/2010 at 08:32, xxxxxxxx wrote:

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

      ---------
      Hi,

      I guess this question should be discussed already, but the forum search doesn't show up anything...

      Is it possible to exclude description resource parameters from xpresso? I don't want all the attribute parameters of my object plugin appearing in the object's xpresso node.

      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/10/2010 at 02:07, xxxxxxxx wrote:

        look for the "Graphview flags" in the docs. I think these should work

        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 25/10/2010 at 07:16, xxxxxxxx wrote:

          thanks. Looks good for configurating xpresso ports, but I can't find a flag that HIDES a parameter in XPresso.

          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 26/10/2010 at 06:21, xxxxxxxx wrote:

            Is there a reason you don´t use the usual GetDDescription() override and use DESC_HIDE? At least that would be my assumption in the first place.

            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 26/10/2010 at 06:47, xxxxxxxx wrote:

              I normally use GetDDescription() for adding resources at runtime. Using DESC_HIDE will hide the parameter also in the attribute manager, won't it? I want single parameters be hidden only in XPresso.

              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 26/10/2010 at 07:19, xxxxxxxx wrote:

                ah ok, so you don´t have an own node (thats why I pointed to GetDDescription as it is also callable for nodes) but for example the default object node when you drag your object into the xpresso editor? Hmm, that is actually quite a good question. I don´t think that it is possible because c4d handles the default node but well, in the end I don´t know for sure.

                Why do you want it to not be accessible in xpresso? Not that it makes any difference on your request but if it´s accessible in the OM it usually makes sense to have it accessed via Xpresso too I guess.

                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 26/10/2010 at 07:47, xxxxxxxx wrote:

                  Generally you're right. But my car simulation has so much parameters and most of them can't be edited or animated in simulation mode after initalisation. On the other hand, there are some runtime output parameters specially provided to use with xpresso. So I want to make the thing a bit clearer.

                  I've just tried to use the graphview flags to sort parameters to xpresso input or output, but that doesn't work for me either!

                  For example
                  REAL     OUT_SPEED { OUTPORT; ANIM OFF; } (res file)
                  can just the same be selected as input port in XPresso. What am I doing wrong?

                  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 26/10/2010 at 08:38, xxxxxxxx wrote:

                    Yeah, I have the same for my fluid plugin.

                    The inport and outport flags are only really applicable to custom nodes of your own not in the objects res files. So the only thing you could do is create your own node and recreate what the default node is doing. Otherwise (at least to my knowledge) I see no chance that you could control what the xpresso node ports of your object will show and what not I´m afraid.

                    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 26/10/2010 at 09:16, xxxxxxxx wrote:

                      puh...

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