'New' release of the Blackbox shell

Question

XZero450 released his customized BBClean for public use. It has some features not used before, since – as XZero450 himself puts it – “never made it into the public releases because they were unpolished, untested, or were incomplete by my standards. Some were rejected by noccy who at the time was in charge of the development”. BBClean-XZ works perfectly well under Windows 7 and comes in a full package including, among other things, a customized bbleanskin.
According to XZero450, bbleanskin “has some tweaks and changes. The major one that comes to mind is that it unrolls all the windows that have been rolled up. This is because I had issues with certain applications remembering that size and thus were no bigger than the titlebar the next time they were started. This will cause Blackbox to take a little longer to shutdown depending on the amount of windows skinned”. There is also a new SystemBarEx version, the plugin XZero “inherited” from Slade Taylor and enriched with various features. Like he says, “it’s only slightly different than the public release”.
The package also includes full rc files and plugins, styles by XZero450 coupled with wallpapers, and other goodies - in short, everything a newbie needs to use the shell right away. And there's even more in store, so stay tuned. The next release of BBClean-XZ may be revolutionary.
BBClean-XZ is now one of the two Blackbox flavors with new characteristics, like split gradients and outline text, that perform perfectly well under Windows 7, the other being Xoblite RC3-4
Download from here  >  http://www.xzero450.com/works/bbCLean-X … custom.rar
** This is, primarily, a new version of Blackbox, and many Arch users use and/or play with other WMs.
And, believe it or not - some people still use MS Windows (for whatever reason) and this Blackbox release works with Windows-7
Last edited by vrkalak (2011-11-04 22:21:12)

Answer 1

I noticed two minor things with the windows version of MakeOTF.
* If a fatal error occurs when using the GUI mode for compiling, the output zero sized binary otf is locked in the file system until you exit the application. This doesn't happen when using the command line interface since the application process always is terminated after each compilation.
* When using the command line interface, or when executing MakeOTF from a script, the "parsing warnings" argument "+w" seems not to be piped to the compiler library after invoking MakeOTF. The "parsing warnings" argument works fine when calling a fpr project file from a script or when compiling in GUI mode.
/mårten