Wootility drag and drop to swap RGB effect order easely(for priority issues)

[tall hollow]

I just updated to the new Wootility RGB overhaul. 1st thing I noticed was the order of the effect layers affects the RGB outcome on the keyboard. I would assume this is due to one being prioritized over the other.

example:
same setting for both profiles only the order of the effect layers changed.
Trail: brightness 100%, 10s, single colour pink
AOE: brightness 33%

1-Trail 2-AOE
(997bc2af51eb7de48926e18238e0cb61000c)
Trail is at 33% brightness after a quick press
only is at 100% when affected by AOE

1-AOE 2-Trail
(0e21c128ff87d7e5b54204573a4475d30e01)
Trail is at 100% brightness after a quick press, even when not affected by AOE effect.

Now this in itself is not an issue. Its great to have more customizability.
The issue is to change from one profile to the other, I have to
1- erase the RGB effect
2- add it back in the correct order
3- manually change all the settings of the RGB effects back to the custom ones.

Dragging and dropping the effect from position 1 to 2 would be more optimal (similar to layers in photoshop).
It would be much easier to mess around with mixing RGBeffects layers this way.

[tall hollow]

also making it clearer which one is prioritized would be nice. I would assume the 2nd one is prioritized over the 1st one from looking at these 2 profiles (since the 1st layer follows the base brigthness of the 2nd one), which is not very intuitive.

[old dock]

theres no priority it is a simple brightness multiplication

the ideal solution since there is no real intuitive solutions in RGB layering is giving all the mixing options color has in the RGB space. im unsure how easy this is to implement or how valuable this is as a feature

[tall hollow]

Intuitively I would assume that putting AOE 1st would make it the main effect. In practice the Trail(2nd layer) is above it and does not get limited by the AOE brightness. it will still be at 100% even tough the base brightness of AOE is 33%. Only when AOE is in 2nd place it will limit the brightness of the Trail to 33%. That was the main reason for my assumption of priorities beeing kind of inverted.

[tall hollow]

hmm. after testing a bit more it seems that this interaction only occurs on with the Trail, RT , the random colors option of the ripple effect and mixing.

[tall hollow]

If you put RT then trail, the RT will not even output on the keyboard. you need to put Trail 1st then RT to get RT to appear properly with a Trail left behind after release.

to make the priorities clearer maybe add the newest layer on the top of the list like on photoshop