Thank you for the response. From an engineering perspective that makes sense. From a user perspective, not sure it does. I can totally appreciate this requiring model enhancements or “shifts.” However, I think we could both agree there is nothing “random” about this.
If the concern is how to communicate a feature to a user, no matter what it is, wouldn’t that just be the UX layer? Seems kinda unfortunate to not entertain features that might benefit users due to concerns over how to communicate said feature to a user. It seems there is already variable-like behavior in the core as a user can use “t” to reference the stock depth in the project settings. Maybe just expanding variables could serve as a potential solution here? I am confident there are probably other ways to solve this problem than going full parametric design. There are many tools out there that are not parametric but allow relational data and variables. Figma is one that comes to mind that is in a totally different field in addition to Fusion.
Thanks for your consideration.