Code::Blocks Forums

Developer forums (C::B DEVELOPMENT STRICTLY!) => Development => Topic started by: Szabadember on April 15, 2007, 01:48:35 pm

Title: Toolbar images *DO* change state
Post by: Szabadember on April 15, 2007, 01:48:35 pm
I have noticed, that toolbar images *DO* change state, but the color of the active save button is only a little bit different than the inactive one (if you don't see it, i could suggest you my eye surgeon :D )

On the attached picture you can see, that between the inactive print button and the active one, there is only one pixel difference (green led on printer). The colours of the save buttons are quiet idenctical too. You shouldn't have blamed others, poor old Bill Gates, poor wx guys.  :P

My OS: Windows Vista Ultimate 32bit, your patched wx2.6.3, april 13 nightly build

I wonder for how long has this been working unnoticed, please change those pictures!!!

I have tested that with small(16*16) and also normal(22*22) toolbar icons

(http://forums.codeblocks.org/index.php?action=dlattach;topic=5673.0;attach=1875)
Title: Re: Toolbar images *DO* change state
Post by: dmoore on April 15, 2007, 02:52:28 pm
have you tried on an XP installation? doesn't work on my XP box.
Title: Re: Toolbar images *DO* change state
Post by: Szabadember on April 15, 2007, 06:47:03 pm
not yet but i will
if it's really not working on xp, why does it work on Vista? Strange, isn't it?  :shock:
Title: Re: Toolbar images *DO* change state
Post by: dmoore on April 16, 2007, 02:23:57 am
possibly part of the WIN API that doesn't quite function according to the spec in XP that has finally been fixed in Vista. I'm sure there are workarounds but the wx guys probably have bigger fish to fry.
Title: Re: Toolbar images *DO* change state
Post by: Grom on April 16, 2007, 03:36:58 am
Problem of eaten egg. :lol:
Title: Re: Toolbar images *DO* change state
Post by: Szabadember on April 17, 2007, 10:40:23 pm
I have tested it myself under windows xp and it is really not working
It works only under windows vista

But i don't think that this is a WinApi problem, i am developing native windows apps using WinAPI and i must say: WinAPi is stable like a rock

Okay, good for me, one less annoying bug...