Re: [Pythoncard-users] TextArea set the foreground color

[<al...@tw...>]

Quoting Cullen Newsom <cn...@sa...>:

> Anyone using colored text in a TextArea or TextField ?
>
> Thanks,
> CN
>

(Sorry about poor formatting - for some reason I can't send email, so =20
I'm doing this through an ugly webmail interface ....)

Yes, I've used it in some apps, but beware it may not work on Mac (and =20
there may be other restrictions on other platforms - I didn't get to =20
try them all out). There was a thread on this topic back around =20
26/05/2006 - it's worth checking the thread if you are running into =20
any problems; my post that started it off said:

The Mac OS X guidelines, indeed the OS provided controls, have some =20
restrictions on what they allow. Since wxWidgets uses these controls, =20
wxPython and PythonCard have the same restrictions. Currently those =20
restrictions are not reflected in the layoutEditor, which can lead =20
users to think there is a bug in the layoutEditor (and therefore =20
PythonCard in general). (btw - I wouldn't be at all surprised if there =20
were indeed bugs in PythonCard and/or the layoutEditor that exacerbate =20
these problems - but so far I haven't seen any confirmed cases).

There probably are lots of such restrictions, but the ones I  have =20
come across are
  - textfields (i.e. single line TextCtrl) does not support setting =20
the backgroundColour
  - textarea (i.e. multi-line TextCtrl) does not support alignment =20
(other than left)
  - button does not support setting foregroundColour
  - button does not (adequately) support setting backgroundColour
          (the rectangle "behind" the button is set, but not within =20
the button    itself - ugly !!)

  It would be good to not only document this somewhere, but (since it =20
will be an easily overlooked footnote in the docs) also make it more =20
obvious to a user when they try to set properties that will not be =20
reasonably honoured cross-platform. This would be especially helpful =20
if they are setting a property while on a system that doesn't really =20
support it - but I think should be done anyway to help people design =20
cross-platform apps if they so desire.

  Would a dialog / preference be too intrusive ?   Something like
    You have set a property that is not supported on your current platform.
    [ ]  Don't give this warning again.                         ( OK )

  and also same thing but "... supported on some other platforms."

  If that was a preference - should it be per-user, or per project ?

  Or would it be better to simply document it as prominently as we can ?




--=20
Alex Tweedly    al...@tw...   http://www.tweedly.net