Support conditional DataMembers in GameStudio
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 7.8k
- Forks
- 1.2k
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 49
Description
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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the existing GameStudio handling for DataMembers, including inherited members and abstract classes or interfaces. Determine how a proposed conditional attribute could evaluate a condition and control property visibility. Done means checked properties reveal their related settings while unchecked properties remain hidden in GameStudio.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- game-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100