Is your feature request related to a problem? Please describe.
Not a problem, more a GameStudio convenience quality of life tweak. The ability to mark DataMembers that will only display in GameStudio when a given conditional evaluates to true.
Describe the solution you'd like
I think the most ideal solution is a new attribute, something like DataMemberConditional(condition to evaluate) that displays when true, and hides when false.
Describe alternatives you've considered
The alternative is displaying all properties at once, which is fine, especially for solo dev but it'd be a nice QoL improvement to be able to do a little GameStudio manipulation.
Additional context
GameStudio does support changing properties based on abstract classes/interfaces and their inherited members (https://www.youtube.com/watch?v=hjScw6Xp2gY), but these are exclusive unless you duplicate code inside. So it works great when you have entirely different properties, but for my specific use case, it's more of "in addition to".
e.g. I have a Tweening library I'm working on, and I'd like a Transform Tween component. Ideally, I would have checkboxes for "Tween Position" "Tween Rotation" "Tween Scale", that when checked, displays Tween settings for the given operation. Currently, I'd have to display everything at once, even if unchecked.
Is your feature request related to a problem? Please describe.
Not a problem, more a GameStudio convenience quality of life tweak. The ability to mark DataMembers that will only display in GameStudio when a given conditional evaluates to true.
Describe the solution you'd like
I think the most ideal solution is a new attribute, something like DataMemberConditional(condition to evaluate) that displays when true, and hides when false.
Describe alternatives you've considered
The alternative is displaying all properties at once, which is fine, especially for solo dev but it'd be a nice QoL improvement to be able to do a little GameStudio manipulation.
Additional context
GameStudio does support changing properties based on abstract classes/interfaces and their inherited members (https://www.youtube.com/watch?v=hjScw6Xp2gY), but these are exclusive unless you duplicate code inside. So it works great when you have entirely different properties, but for my specific use case, it's more of "in addition to".
e.g. I have a Tweening library I'm working on, and I'd like a Transform Tween component. Ideally, I would have checkboxes for "Tween Position" "Tween Rotation" "Tween Scale", that when checked, displays Tween settings for the given operation. Currently, I'd have to display everything at once, even if unchecked.