ML Panel v Profile

i think the problem is that you have two identical User min/max ranges in Color Wheel Mode. That might be the overlap Eos complained about...

Yes. If you look at the picture from the ML panel I can't select the Rotate cell to see my two choices. It's going to be one of those dumb things I overlooked or got wrong 

Even after fixing the ranges?
Any chance you would be willing to share the show file?

No problem. Its about the barest bone thing I could hack.Experiments 2020-07-20 13-16-04.esf

Thanks!  I think I figured this out.
1. In color wheel mode your user min/max match.  It gives an error that ranges cannot match.
2. When attempting to make this a mode of color select you get a message that when using a virtual mode ranges and user ranges must match each other.  Yours do not. 

Error: 

Fixed DMX and User ranges (sorry I did the wrong name!): 

If you make the DMX and User ranges match each other in the Color Wheel Mode then this should work.  We just need to resolve the two errors it was giving you.

I do think there is an argument here that the errors should occur sooner and you shouldn't be able to bypass them if they will render to ranges useless.

Excellent. Making your changes sorted it all out. Is it always the case that these ranges should match. And, when I tried to edit I got the "can't edit this parameter". The only way I could unhook the parameter was to delete the modes in the wheel mode parameter and wipe out everything! Is there a way that I can 'unhook' the Color Select from the Wheel mode without having to delete all the contents? I.E. Just remove the conditional statement temporarily. Now I have to put this in bench notes. if you're not doing this stuff everyday it's easy to forget.

They have to match because it is a virtual parameter, in this case (DMX=0), but if you were using a DMX address my understanding is that they would possibly always need to match but I'm not 100% clear on this.  I know that it is something we are working on improving.

At this time you have to remove the part and put it back on, but this is also something we are working on.

They have to match because it is a virtual parameter, in this case (DMX=0), but if you were using a DMX address my understanding is that they would possibly always need to match but I'm not 100% clear on this.  I know that it is something we are working on improving.

At this time you have to remove the part and put it back on, but this is also something we are working on.

All makes sense. And understand about the last part. Thanks to you folks for getting me over the hump on Profiles Modes.