I think I know the answer to this but I need to ask it anyhow to confirm. When you make a Global Parameter, you can't assign it to a Category per say, like you can a Project Parameter, and Global Parameters can only interact with higher level "Project" Information - correct? So I can't write a formula for a Global Parameter that looks into a specific family for that parameter and it's value, because the parameter really doesn't know where to look for it?
Thanks!
Gelöst! Gehe zur Lösung
Gelöst von dbrainard. Gehe zur Lösung
...but you can assign a Project Parameter to a Category and tie a Global Parameter to that Project Parameter.
Thanks Barth,
I think I see where you are going with this. There are some parameters that make sense to be a Project Parameter but there are still many parameters within our loadable families that make better sense to stay within those families. What I initially set out to do was to make a conditional formula at the project level that would read default values within certain loadable families/categories and then change those values on the fly if they met a new criteria at the project level. I'll find another way.
I like the ability to do formulas/calculations in global parameters, it's just too bad that they can only interact at the project level exclusively and that we can't pre-link loadable content parameters to them ahead of time. I wonder if having a global parameters file (kind of like a shared parameters file) might allow us at the family level to pre-plan for project interactivity. Maybe I'll drop in a suggestion at the new feature request page.
Thanks!
Sie finden nicht, was Sie suchen? Fragen Sie die Community oder teilen Sie Ihr Wissen mit anderen.