Bonus bug: you must also left-click on the color you want to change first (Birth, Min, Death) so your editing is taken into account.
After changing the 3 values for RGB, I realized the color didn’t change at all. I needed to left-click on Birth, change RGB, then do the same for Min and Death. I wish we could copy-paste colors to make this faster, but that would be a suggestion for another thread.
For now, to focus on the UI issue: to avoid having the user edit a “ghost” color for nothing, maybe gray out the RB HSV interface until a color is actually selected. Alternatively, allow editing color “in the void” but then add a small button or drag and drop system to assign the temporary color to Birth, Min, Death color.
Another bug: I right-clicked on Birth, Min, Death color and noticed there was a popup similar to Alpha, RGB/HSV values, where you could enter a number. I thought it was great to enter a hex color, allowing me to copy-paste colors from another app much faster. It turned out the field only supports numbers, which don’t make sense for a color, and therefore: a. entering an actual number like 100 does nothing b. entering a hex like df7126 or #df7126 makes the app crash with error:
############################################################################################
ERROR in
action number 1
of Step Event2
for object uiChanger:
unable to convert string "df7126" to number############################################################################################
gml_Object_uiChanger_Step_2 (line 27)