08.03.2005, 15:57:43
(This post was last modified: 08.03.2005, 16:00:59 by Bobingabout.)
thing he means with meaking new colours optional is:
an activation tag souch as "CostomMenuColors=yes" and a new list [MenuColors] containing pointers to the names to use IE:
0=Gold
1=DarkBlue
2=DarkRed
3=Purple....
and so on, allowing you to specify only the ones you want on the menu.
problem is what happens if that list is not there?
also, getting it to display the colour on the menu isn't easy. menu needs a BGR(RGB in reverse order) and the colours are in the unique YR method of HSB. meaning, easiest thing for PD to do is make another list to display the costom colour.
or, something else we been working on, finding the HSB2RGB conversion algorithms, or writing our own onto the end of the list.
another reason why optional is because theres no easy way to add more unless you simply hard coding more into it, in which case it would only be a couple more, and you'd probably still have the colour on the menu problem not matching the color in the list if you wanted to change it.
an activation tag souch as "CostomMenuColors=yes" and a new list [MenuColors] containing pointers to the names to use IE:
0=Gold
1=DarkBlue
2=DarkRed
3=Purple....
and so on, allowing you to specify only the ones you want on the menu.
problem is what happens if that list is not there?
also, getting it to display the colour on the menu isn't easy. menu needs a BGR(RGB in reverse order) and the colours are in the unique YR method of HSB. meaning, easiest thing for PD to do is make another list to display the costom colour.
or, something else we been working on, finding the HSB2RGB conversion algorithms, or writing our own onto the end of the list.
another reason why optional is because theres no easy way to add more unless you simply hard coding more into it, in which case it would only be a couple more, and you'd probably still have the colour on the menu problem not matching the color in the list if you wanted to change it.