https://www.displayfusion.com/Discussions/RSS/?TopicID=50e09941-be80-487a-ab4f-db96c1fd6e0a DisplayFusion RSS: problem with taskbar Sun, 07 Jun 2026 04:30:16 GMT en hourly 1 https://www.displayfusion.com/Discussions/RSS/?TopicID=50e09941-be80-487a-ab4f-db96c1fd6e0a https://www.displayfusion.com/Discussions/View/problem-with-taskbar/?ID=50e09941-be80-487a-ab4f-db96c1fd6e0a#4 Sun, 25 Jan 2009 17:37:08 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/problem-with-taskbar/?ID=50e09941-be80-487a-ab4f-db96c1fd6e0a#4 DisplayFusion Excellent! It turns out there was a bug with the way DisplayFusion was reading the contentmargin property from the taskbar button theme. I have corrected this for Beta 16 and it looks perfect now with this theme and all the others I tested with. ]]> https://www.displayfusion.com/Discussions/View/problem-with-taskbar/?ID=50e09941-be80-487a-ab4f-db96c1fd6e0a#3 Sun, 25 Jan 2009 13:55:06 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/problem-with-taskbar/?ID=50e09941-be80-487a-ab4f-db96c1fd6e0a#3 DisplayFusion I'm using "Vista CG" visual style. You can download it from:

http://www.crystalxp.net/galerie/en.id.505-vista-cg-snakeuk-visual-styles.htm ]]> https://www.displayfusion.com/Discussions/View/problem-with-taskbar/?ID=50e09941-be80-487a-ab4f-db96c1fd6e0a#2 Sat, 24 Jan 2009 19:26:25 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/problem-with-taskbar/?ID=50e09941-be80-487a-ab4f-db96c1fd6e0a#2 DisplayFusion Thanks for the heads-up. Which theme/style are you using? ]]> https://www.displayfusion.com/Discussions/View/problem-with-taskbar/?ID=50e09941-be80-487a-ab4f-db96c1fd6e0a Sat, 24 Jan 2009 18:07:47 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/problem-with-taskbar/?ID=50e09941-be80-487a-ab4f-db96c1fd6e0a DisplayFusion Hi, I met this "bug" today while I was trying DisplayFusion beta 14 taskbar with different visual style on Windows XP.

Sometimes happen this:

And sometimes nothing:

I think this is caused by the font, but it is only a supposition. ]]>