bbWinSkin - latest version 1.21 (2009-06-02)
exclusions.rc - latest version (2009-06-22)

• expanded styleFont option
• safeMetrics handles oversize Titlebars
• styleParsing overhaul - only bb4win skinner that displays "old syntax" frame & borders as per bb4nix
• adjustable snapToEdge distance

bbWinSkin 1.21 for transparency addicts (with higher-specced boxes) is over there

Tested on Win95->Vista. (Win95 users watch out for crashes on Restarts)


Enjoy!


unkamunka - #bb4win

Out of lack for better words...

I love you.

Hm, seems to be working...
(tried it with Noccy's November build).

I was supposed to test this build, but I've been too busy. Sorry

Ditto. Heck, although I've D\L this final build, I still haven't had a long enough pause to install it

As stated, your earlier feedback was very helpful.

It was a pleasant surprise to find it loading smoothly onto an (old & dusty) Win98 box under bbLean.

After that - & the feedback from the other beta testers - it seemed good to wait no longer.

How about such feature: to show small popup with window' coords, while moving window, like in *nix ?
I think, it would be great

Is this new behaviour, or has this always been the case?
I just noticed that this version appears to not like the "-" to distribute buttons to the left and right corners of the window bar: "4567321" creates a "456"..."7321" look, whereas "4567-321" turns into "456"..."732", dropping the Close button.
That's actually a bit annoying as it won't let me arrange the buttons any way I like, rather forcing me to adapt the 3+4 format.

problem fixed by mini-man.... great work on this new version unkamunka, its teh sex!

A bit of history: the predecessor of LeanSkin - WinSkin - was prone to instability. The original LeanSkin forced a 3:3 split. The original LeanSkin Mod did the same (with a limited fixed icon option being added later).

The update has changed the split to 3:4 & expanded the icon drawing. 3:4 should cater for most situations. (A left-hander can use 1237654.) The LeanSkin that ships with bbClean offers only 6 icons - albeit allowing you to have > 3 on the left & > 4 on the right.

In principle: the more options are added, the less well the plugin performs. The bbClean version parses 15 options to allow - say - a 4:2 split. The LeanSkin Mod update parses 7 options & allows all possible buttons to be displayed. On the fly parsing for, say, a 5:2 split would require > 15 options to be parsed.

At the end of the day, adding a single button & allowing stylists a greater range on such things as frameWidth was considered a higher priority.

Just out of curiosity...

The title of the thread is' bbLeanSkin Mod - StyleMaker update'.

Does this refer to bbStyleMaker and if so, in what way? If so, the update may be obvious to a bbStyleMaker user but, not being one of those, I'm kind of lost as to what that means.

StyleMaker is a "play on words":

• For all stylists & users, the skin is more backwards compatible for handle & frame syntax. Among other things, you can now load a Fluxbox style (or one of the older bb styles) & not inevitably have to play around with the file to get windows rendered correctly.
• Some folks (but by no means all) seem to prefer really "chunky ornamentation" around the window. Under previous skins, if frameWidth (or any of its syntactical equivalents) were set > 4, the buttons were "crushed to death" - as a result of a knockon effect to the title bar dimensions. This (to all intents & purposes) no longer happens.
• For bbStyleMaker users running any of the available branches, AFAICS this version of LeanSkin runs no differently from any of the others. OTOH if someone releases any of the bbLean builds with (the equivalent of grischka's original) line 599 in Blackbox.cpp commented out, they will notice that the frameWidth control is no longer "broken".

OK, I get it now.

Thanks unkamunka

This being said, an updated BBStyleMaker would be welcome by all, applying to all BB elements and not just bbleanskin...

AFAIK grischka (last known sighting - 24 October 2006) is the only one who has ever seen the source code.

It's not impossible to try and build another version from scratch - depending on time priorities.