i don't know
Published on March 30, 2006 By David Lyncheski In Skinning
what is styler toolbar?
whare do i get it?

Comments
on Mar 30, 2006
Link

I believe this is what you need.
on Mar 30, 2006
If you use windowblinds set the program in "toolbar mode" otherwise it will mess your windowblinds skin
on Mar 30, 2006
If you use windowblinds set the program syler in "toolbar mode" otherwise it will mess your windowblinds skin
on Mar 30, 2006
Sorry, double post
on Mar 30, 2006
By the way, it's $17 for full, or $10 for just the toolbar after the trial. I used the trial, but I don't think it's worth buying. Windowblinds is $20, so $10 for a toolbar seems kind of steep by comparison.
on Apr 16, 2006
If you use windowblinds set the program syler in "toolbar mode" otherwise it will mess your windowblinds skin

Well, I tried the Evaluation version of Styler 1.38 with WindowBlinds 5.01 with the "toolbar mode" checked and it still raised havoc. I don't mind paying $10 for the "Styler Toolbar" standalone version, but I don't want to spend $10 only to find out it's incompatible with WB.

Is anyone running these two applications with no problems?
on Apr 16, 2006
Works great for me...no problems at all Hapkido. I've been using it a few months and no problems with any WB skins.
on Apr 19, 2006
Well, I went ahead and spent the $10 for the "Styler Toolbar" license, installed it and I'm having the same problem as I did with the Evaluation version. The problem is on startup/bootup. Styler is one of, if not the last item to load and when it does, it kills WindowBlinds and parts of Explorer. The only way around this that I have been able to find is to first load the default "Classic" skin and then reboot. After Styler loads, then change to the desired WB skin. After that, everything works just fine. I can even exit Styler and start it again, over and over, and it has no negative effects. In the "Event Viewer", it consistently shows "explorer.exe" as having a page fault error when Styler loads.

Although this is admittedly a nuisance; a serious one IMHO, rather than one that causes serious errors to my O/S, I do think that it was $10 wasted. If anyone has a fix for this issue, I would surely like to hear it.
on Apr 20, 2006
I have resolved this issue, as best as I can tell. The problem hasn't reoccurred since I made a configuration change on my system. In short, I enabled the "Theme" service and set it to "Automatic", which had been disabled for quite a long time. For more on this, see here: Link
on Apr 20, 2006
Cool. I'll keep that in mind in case anybody else has a problem. Thanks for posting your solution.