First of all, previous topic is here.

The main focus of this update was making modules as independent as possible (eliminating name clashes), while still maintaining backwards compatibility. User friendliness is also somewhat improved.

A changelist since the previous (0.9.89j) version:

Made module membership implicit, introduced the notion of 'caller module'
Now, the modules are not only control-scriptfile associations, but rather a group tying controls and related static variables together. This also means that there will no longer be name conflicts between identically named controls in separate modules. Now, the name that identifies a control is ModuleName:ControlName, or :ControlName in the case of the global module. When only the controlname is used in itself, it assumes that the default module is being targeted. The default module is either where the broam came from (the caller module), or if it's a BBI broam not sent by BBInterface itself, the module set with the Module SetDefault command. The caller of a broam is one of the following, if applicable:
- the current module that's being loaded, in case of a Module Load command.
- in case of a broam agent (BBI buttons, for example), the module of the control the agent is mounted to.
- in case of a config line being executed, the caller is whatever called the Plugin Load command executing the file.
What all this adds up to, is that broam calls stay 'inside' modules, unless explicitly specified. This should be backwards compatible with scripts from previous versions most of the time.

Plugin Load [Script] from ScriptFile.bbi into Module - adding 'into <modulename>' to the end of a Plugin Load command will allow setting of the caller module during the loading of that particular file or script.

Control Create Module:Type - As you can see, the control type is prefixed with the module name to designate a target module.
Extended Edit Module menu - Allows easier editing for more parameters of modules.
New module entity - changed syntax, pay attention. New commands are used now.
-- Module Load <file> - Loads the module specified by <file> into the memory.
-- Module Create - Creates a new, empty module with a name 'Module#'.
-- Module Toggle <name> - Turns the targeted module on/off.
-- Module SetModuleProperty <target> <property> <value> - Set either the Author or Comments of a module.
-- Module Edit <target> - direct RC editing.
-- Module Rename <target> <newname> - Self-explanatory.

DroppedFile 'properties' - .Path, .Name, .Extension, .Filename, when used like properties of the DroppedFile, you can extract various parts of the data provided.
Split commands in config files across multiple lines with '\' - So that long @Script commands will be easier to use.
Conditional expressions. ( ?: , <, >, =, >=, <=, !=, &, ^, | ) NOTE: Previous '?' token changed to '%' - You can use these as their usual counterparts ( &,| are binary AND and OR operations. ) Of greater interest would be the '?:' ternary operator, used like (condition) ? (option1) : (option2), and evaluating to option1 if the condition is true (non-zero), and to option2 otherwise.

Extra tooltip info (X,Y,W,H)
Custom bevels - available bevels are "Flat", "Raised", and "Sunken".
Text shadows - automatically generated, just like xoblite. Supports the shadowColor field on the newest bbleanmod as well.



DOWNLOAD IN ATTACHMENT.

EXAMPLE SCRIPT FOR SOME OF THE NEW FEATURES HERE.

The shadowing looks great.. very cool.

I did have an initial compatability issue with startup of the plugin, but nothing was damaged. So if anyone gets this.. don't be too alarmed.

I also noticed the Global OnLoad and OnUnload edit boxes in the menus.. Was that always there? In any case... That's a cool addition too.

Great job on this Pkt-zer0

Just out of curiosity, how does Xoblite determine shadow color? Is it based on the colorTo or color2..

I don't know how this happened, but after updating to this version tcl-bb crashes bbLean every time it loads. It's telling me my init.tcl is no good, and that TCL is probably not installed.

I've reinstalled tcl-bb. I also tried commenting out my tcl procs that send broams to BBInterface, but it's still taking blackbox down everytime I try to load it.

Any ideas on why this would happen?

Which version of tcl-bb are you using? Mine is working fine. I have tcl-bb 2.4.8.2

That's intentional. I bumped up the version checking to v0.9.9, since some of the syntax IS indeed incompatible, namely the commands related to modules, and that the token used for 'current value' is now '%' instead of '?'.

Takes the average of color and colorTo, then decreases each color component by 0x10. I used 0x20 there instead, for a bit darker shadows. Though it took quite a bit of time, to search through the xoblite source, due to its HTML format.


What the. I don't use tcl alongside bbi myself, but I know that enough people do. I also didn't make any changes that would implicitly alter compatibility. Were you using v0989j before?
You might also try loading the plugin without an RC file (just to see if they screw up by default, or something else is the matter), or try using another blackbox branch...
There's not too much I can think of that'd make BBI kill other plugins.

The only thing that may.. and it's just a small 'may' cause a crash in a plugin, is if you accidently loaded a plugin twice that doesn't support that. Tcl-bb can be loaded into a slit and then loaded again normally.

So if tcl-bb was accidently loaded into a bbi frame and then loaded via standard blackbox plugin method, that could crash it.

How difficult would it be to create a shadow calculator for bblean based on that type of formula? Before I got the above answer, I actually used a magnified color picker to grab the shadows from a bbi object to apply it to the rest of my bblean objects. lol

It's five-six lines of added code in bbleanmod or so. It really is simple. I like the implementation of that feature more in bbleanmod than in xoblite, since it uses a provided shadow color, rather than a yes/no shadow toggle. You could easily inline a shadowcolor generator into the function call, anyway, kinda like this:


The possible incompatibilty arises from bbleanmod storing a shadowcolor for each style element... haven't tried compiling BBI with that header yet, but I guess I'd be lucky if that were actually backwards compatible as well (the modified bbleanbar/skin didn't seem to be)

EDIT: So far, some quick tests with the newest bbleanmod, an older mod, pure bblean 1.16, and xoblite, show that the shadowColor part works correctly! As in, recognizes custom shadow colors in the newest bbleanmod, and recognizes the lack of them in all the other cases, substituting auto-generated shadows. Nocd5 hasn't replied on this matter yet, so I'm not a million percent sure if I'm doing it right, but it seems that way at least. Be back in a few with an update.

well it looks like rebooting cleared it up... I couldn't think of any good reason for this to be happening either, after reinstalling both plugins, using the default rc for BBi etc etc.

My only guess is that the old tcl-bb didn't unload properly when I restarted bbLean at some point.

I'm chalking it up to voodoo (but I'm cool with it being called user-error if it's less stressful )

wow great pkt-zer0

Alright, just putting this up here as a test. People using the newest bbleanmod would now be able to have their shadowColor settings take effect. Everyone else should see no difference.
Will add it to the proper archive if people have no problems, will take it down if there are incompatibilities. As stated before, it worked properly for me under two different versions of bbleanmod, bblean 1.16, and xoblite.

EDIT: Minor change in the shadowColor-support detection. Proabably this is the proper method, not the other one.

EDIT: Removed this version, since the shadow-detection does seem to work fairly good. Merged into the main source, and all.

Shadows work under xoblite?

The shadowtest version works just fine for me. And it's great that I don't have to go back and match my styles shadows to my bbi ones ... hehe

Are you being sarcastic?
It's independent of the branch you're running on, since it only uses the basic text drawing routines. So you can actually have shadows in BBI on a shell that doesn't even have that function built in.

How is it possible to add the BBSysmonPlus to a frame? Also, how or is it possible to show cpu % in digital? Thought I saw a screenshot of somebody's setup that had it.

Thanks