common tasks not skinned when exporting skin via style builder.....help

I take a .theme file that has a skinned common taks pane (left of explorer window) and I edit minor things but when I compile the skin into an msstyles ( only option with stylebuilder I even did this process without editing the file)my common task pane is not skinned.

is this a problem with stylebuilder? Can somone suggest a product that I can use to edit a .theme file and save it with out losing the ability to have the common tasks pane skinned?

Thanks

Locked Post

Advanced Search

Watch this post

Do not email me updates for this post Email me updates for this post

Successfully updated karma reason!

how about you develop your skins for WB and style builder all together.. You'll find very few styleXP users here. Those that do use msstyle skins probably just use the free Dll patch from the web.

Successfully updated karma reason!

I don't use style xp nor webblinds takes too much resources and too much problems I do what youmentioned the dll patch by neowin

I just wnat somethign that I can edit the current .theme or msstyles files and spit it back out and no not in weblinds format

I just wnat my system to be clean and to less memory, that is why not using webblinds

Successfully updated karma reason!

Sign Up or Login and this ad disappears!
There are many great features available to you once you register. Sign Up for a free account and browse the forums without ads.

c242

Join Date 03/2001

+383

lol, You are aware of the fact that Windowblinds uses only 2 MB of memory wheras the system ressources You use with a .msstyle are hidden in one of the svchost.exe tasks ? I would recommend this https://www.stardock.com/products/windowblinds/history.html (especially "Myths & Facts about WindowBlinds")as a good read. You won't find Stylebuilder help here.

Successfully updated karma reason!

Ok fine I'll give it a try and come back and give my honest opinion
hopefully there might be the mix theme by kol for wb

Successfully updated karma reason!

Well one thing is damn obvious nothing can skin widonws like windowblinds...........I mean it covers everything

But taking advantage of the UIS2 explorer gets a frigging hit I notice these things opening windows takes longer even thought its fractional ( even though I have the a 9600 pro, p4 3gig, 512 RD ram, raptor 10,000 rpm), so like I said yes it does use up resources maybe not that much memory, since I was going from neowins uxtheme.dll hack to windowsblinds 4.2 more memory is being used not much but there is no such thing as commit charge going down after using windowblinds.
I am using litestep too and sometimes opened windows aren't skinned.

End of the day I am sticking with it mainly because skin studio can skin absolutely EVERYTHING on windows (as for the margins thing real annoying), and lets not forget that roll up thing damnnnnnnnn its cool so there is my final verdict.

Successfully updated karma reason!

Man those are some impressive stats on your system.. Why might I ask did you get such high end components and then skimp on the RAM? 512MB is really skimping if you run ANY memory hungry apps. The price of RD RAM has come down dramatically recently, you should look into upping to at least a Gig. You won't be disappointed. I have a Gig in my laptop and 1.5 Gigs in my desktop and I NEVER have any slowdowns caused by running lots of proggies..

Just my .02 cents worth.. Take it or leave it, it's up to you.

Successfully updated karma reason!

yeah your damn right I need more ram lol.............but in 3 years (time I bought my ram) my rd ram sticks here in canada are still the same freaking price 145 cad for 256 mg(pc800).

Hey let me ask you since you have so much ram do you ever turn off your page file, or did you get bad results?

Successfully updated karma reason!

I run windowblinds with a p4, radeon mobility 7500 w/ 32mb, and 512 mb mem. I notice little difference between windowblinds and the patch uxtheme. The only difference I notice is with some wb skins running better than ustheme ones.

Successfully updated karma reason!