Feature idea: Condition driver for DT Smart Object

[TheGameratorT]

Motive

In my avatar I have multiple object toggles that depend on other objects being disabled and those same objects also depend on others being disabled but I want them to stay selected in the menu so they automatically come back when I disable the dependent objects.

My current approach to this problem is to define 1 smart object with the menu toggle MenuParam and another one with just the unsynched condition parameter Param which has its own animator layer to toggle it ON and OFF depending on the condition that I set it. An example condition that would make Param be 1 could be MenuParam && Param2.

But doing this manually takes a long time and can get confusing.

Here is an example of Stockings that are only visible when the Bunny Suit is set.

Picture 1

Picture 2

Picture 3

Picture 4

Example DT Smart Object

This is a driver that I believe would be the solution to this problem.

Driver: Condition

Parameter:
	Unsynched.
        For usage in animator and internally with other smart controls.
	Contains result of all conditions, 0 or 1.
	Can be set by the VRCAvatarParameterDriver on Disabled, Enabled and Prepare Disable.
	Does not need to be generated if empty and not used by any other smart controls.

Conditions:
	Group 1:
		<DT Parameter Slot> > 0
		<DT Smart Control> = 1
		<DT Smart Control> = 0
	
	Group 2:
		<DT Parameter Slot> < 0.5
		<DT Smart Control> = 0
		<DT Smart Control> = 1
	
	(Each group will do OR with eachother)
	
	Add Condition Group

Control: Binary

Object Toggles...
Property Groups...
Cross-control Actions...

With this, picture 2 and 3 would not be needed.
This would also allow for objects to be enabled by default and disable when the menu is unselected, however a way of inverting the condition on the toggles would probably make more sense for that as each condition driver requires a new animator layer.

Considerations

Maybe a check on using the condition smart object on itself must exist to prevent an infinite recursion.

P.S.

I am really liking this tool and I see the potential on it, compared to VRCFury and Modular Avatar this was the only one that got the closest to my needs, so thank you a lot. I'd like to try to implement this driver myself but I am still not sure if I have time to get used to this codebase and I'd also like to know first what you think of it.

[poi-vrc]

Thanks for your request. I have always wanted to create a driver based on conditions like you stated above. But I am currently working on other QoL refactor on the tool so I might not be able to implement this for the time being.
If you could read the code base and contribute to the code, it would be much appreciated. We could reach discord to talk more about the details if you are interested.