|
Re: disabled/read-only Text theming [message #122253 is a reply to message #122242] |
Mon, 23 February 2009 10:10 |
|
Hi Jim,
I'm very thankful for comments like this, as they reveal what people are
actually struggling with.
Jim Tilley wrote:
> Hi,
> I would like to set the background color of a disabled and/or read-only
> Text widget using CSS theming.
For the read-only part of your question, the Text widget does not have a
CSS state "read-only" yet. If you need it, feel free to file a bug for
this problem. It shouldn't be hard to implement this state.
> text1.setEnabled(false);
> text2.setEditable(false);
>
> The CSS code is:
>
> Text:disabled {
> background-color: gray;
> }
This should work, but I see that it currently doesn't. There must be a
bug in the theming. Could you file a bug report for this too?
Best regards, Ralf
|
|
|
Re: disabled/read-only Text theming [message #122264 is a reply to message #122253] |
Mon, 23 February 2009 10:30 |
|
>> text1.setEnabled(false);
>> text2.setEditable(false);
>>
>> The CSS code is:
>>
>> Text:disabled {
>> background-color: gray;
>> }
>
> This should work, but I see that it currently doesn't. There must be a
> bug in the theming. Could you file a bug report for this too?
The reason is that the :disabled state is missing from most widgets,
including Text. As a result, *:disabled works, but Text:disabled
doesn't. However, this is worth a bug.
Ralf
|
|
|
|
|
|
Re: disabled/read-only Text theming [message #122536 is a reply to message #122507] |
Tue, 24 February 2009 20:20 |
|
Hi Jim,
Jim Tilley wrote:
> Would the Text read-only state also be fixed under bug 257548 or would
> you like me to open a separate bug?
No, that's a different issue and should be reported in a bug of its own.
Thanks, Ralf
|
|
|
Powered by
FUDForum. Page generated in 0.03602 seconds