Re: Image transparency on a disabled button




"Schelte Bron" <nospam@xxxxxxxxxx> wrote in message
news:433b04a0$0$53256$dbd4f001@xxxxxxxxxxxxxxxxxx
> Jeff Godfrey wrote:
>> Thanks for the input. That's a pretty neat idea (and it seems to
>> work well) though in my particular case I don't like the look of
>> the b/w images on the disabled buttons. I suppose I could do
>> something else to the image in the "dim" proc, though I'm not sure
>> what - maybe I could manually dither
>> it. But, that begs the question - why should I have to?
>>
> You can of course provide your own custom made disabled version of
> the icon too. But this is just a simple way that doesn't require
> any artistic talent, of which I don't have a whole lot.
>
> Judging from a mail on the tile-dev mailing list Joe English is
> planning to completely remove the stippling code. The button will
> then just display the icon you specify. If you want some other
> image to be displayed when the button is disabled, you have to
> specify that. That seems to me the more Tile way of doing things
> anyway.
>
>> Anyway, thanks for the suggestion and the code. Out of curiosity,
>> *why* do you b/w the images on disabled buttons? Do you just like
>> the look, or is it to combat this (apparent) transparency issue?
>>
> I didn't like the look of the stippled images. Especially, as you
> mentioned, when there's transparent parts in the image. Because I
> normally work on KDE I just tried to mimic the appearance of
> disabled buttons on KDE.

Thanks Shelte,

As I'm using Tile, I'll just provide another image for the disabled state -
as I think I can come up with something that I like better. I am still
curious though (with regard to Tk) whether something is broken with respect
to image transparency and disabled widgets. Again, Tk *and* Tile both
exhibit the same (incorrect?) behavior.

If anyone has any input, I'd be happy to hear it. If someone doesn't show
me that the problem is *mine* instead of *Tk's* in the next few days, I
guess I'll file a bug report on SF.

Thanks again.

Jeff


.


Quantcast