Thoughts on hierarchical options for RGB scripts

[hansjuergen]

In my perception, there are concerns that the amount of RGB matrix functions becomes too large to be reasonably manageable at some point in time and I would agree as they are a powerful feature to enable dynamic shows.

What would you think if a hierarchical UI would be used, similar to what we provide in the Fixtures selection? It could look like:

+ Base Matrix Programs
- - Audio Spectrum
- - Image
- - Plain
- - Text
+ Figures
- - Blinder
- - Balls
- - Marquee
- - Circles
+ Static Color Patterns >acceptColor = 1>
- - PlasmaColors
+ Color Change Patterns <acceptColor = 2>
- - Even Odd
- - Stripes
- - Stripes From Center
- - Vertical Fall
- - Waves
+ Direct Color Patterns
- - Plasma Direct
- - Marquee Direct
- - Balls Direct
+ User-Defined
- - <as read from user directory>
- <uncategorized>
- <uncategorized>
- <uncategorized>
...

The most maintainable way of achieving this could be an optional "algo.category" property to dynamically make up these "folders", like:

Code: Select all

algo.category = "Figures"

I am not sure though, which categories we would agree on.

What would you think? Is this useful, doable, achievable, backward compatible?

[MichelSliepenbeek]

In a User Defined RGB Matrix you also have the possibility to set the "algo.category" property, so i would not go for a seperate category "User Defined".