Allan,
READ THE BLOODY DOCUMENTATION!!!!!!!!
while (reading) {
;-) ;-) ;-);
}
When your cursor goes over amy object in FormPreferences you get a little bit
of text. Read it. Act upon it!
Now have fun.
Angus
> Okay, will you help me with the en_EN and then we can take all that
> misspelled stuff and make it en_US.
Certainly.
>
> > > 2. It doesn't work. I took a quick look at the input processing in
> > > Colors::input() et al and it seems that the Modify button is
> > > disabled almost everywhere unless V=0 or 1 and S=0.
> > >
> > > Hopefully you are already aware of this, Angus, because I can't repeat
> > > your claimed colour setting tests.
> >
> > It works fine. You've simply chosen a grey colour and tried to move the
> > dials. It'll remain grey for all eternity until you change the
> > Saturation. Alternatively, if this is too complicated for you ;-), just
> > click on a colour in the browser.
>
> Unfortunately, the steps you describe (clicking the colour wheel and
> changing the saturation) are exactly the ones I followed. As I said the
> only way I could get the Modify button to be activated was (depending on
> the thing I wanted to change the colour of) to select either black or some
> shade of grey.
>
> Clicking on the colour wheel deactivates Modify.
> Spinning the colour wheel deactivates Modify.
> Sliding S deactivates Modify unless S==0.
> Sliding V deactivates Modify if (S!=0 and the object == GUI_???)
> or (the object != GUI_??? and V corresponds to some limited
> discrete grey colours)
> Clicking Apply has no apparent effect after changing colours even on those
> rare occasions when Modify has been active and I've pressed it.
> Shouldn't Apply be deactivated until after Modify has been pressed when
> fiddling with colours?
>
> Perhaps, this helps clarify the situation.
>
> FYI, I tried this with the GUI_XXX options, all the inset background
> colours, the footnote colour, the background colour, the text colour and
> the cursor colour.
>
> Allan. (ARRae)
