Hello,
there's one more of my plugins. Try it if you want and if you find it usefull, but I am sure it must be full of bugs. It cannot be slitted for now, because I have problems with making plugins slittable (if you're interested, see here: http://www.lostinthebox.com/viewtopic.php?t=2372). Enjoy!

http://pitris.me.cz/?view=BBlean

Very nice, looks like it has a lot of potential. I don't have need of it myself, but I remember a number of people requesting something exactly like this. Nice one.

Beautiful!

nice plugin...

but it is not slitable...

Cheers,

Not only not slitable but it will throw an error message if you even try and load it in the slit. It would seem better programming practice to just ignore the SlitWnd that's passed, not call SLIT_ADD, and then just call your beginPlugin.. Had to update bb4blux (a year since I did that last) just so it could work around that.. *sigh*

Other than that, great idea, awesome plugin!

I might just use it if there was a 'slimmer' version of it...yes, yes, I did the rc config like mad...but it looks choppy when it's slimmed down..as in...height.

@ tresni:
See, at least you updated. I'll correct it soon.

@ /\/\inimal:
What exactly do you mean with choppy? Can you give a screenshot?

Sorry about that pitris, my post was a little more..rude.. than I intended it to be. But yeah, if you don't want to use beginSlitPlugin or beginPluginEx do I what I did in WorskpaceStyle

Works like a charm and users usually don't know the difference (except that even if they load it with & it won't go in the slit).

P.S. that code is from memory as I am at school atm.

BBnettraffic 0.0.2 is now slittable.

BBNetTraffic is very useful for me, but i can`t find out, is there any way to config cost value, for example, im paying 5.95 RUR per 1 meg, but looks like plugin doesnt undestand dots, so it counts only 5.
Also the final cost is displaying for example as "30.20", but the real cost is 3.02 how can i tune it?
If you will continue developing this great plug, can you add a feature to count traffic this way:
i pay from 7:00 to 24:00 - 6 RUR, and from 0:00 to 7:00 - 3 RUR
can you add this feature? Sorry for my bad english.
P.S. Your screensaver is also very nice.

Looking great pitris, however I found two minor bugs/issues:

(1) The beginPluginEx entry point is not handled correctly. You see, while it may not have been documented properly in the SDKs, use of beginPluginEx assumes that the plugin handles its own slit status, i.e. whether it should be docked or not, rather than relying on the loading parent to do that (as was the case with the older beginSlitPlugin which was used if the plugin was &-loaded in plugins.rc). In other words, the plugin should not automatically dock itself to the slit when the beginPluginEx entry point is used (as was the case with the older beginSlitPlugin), but based on a setting in its own configuration file.

(2) The plugin does not seem to properly remove itself from the slit when it is unloaded. Make sure you're performing a...
SendMessage(hwndSlit, SLIT_REMOVE, NULL, (LPARAM)hwndPlugin);
...during endPlugin().

That said: Nice plugin, keep up the good work!

BR//Karl -> qwilk

Sorry about the late reply. Totally forgot about this thread.

Well, I unloaded the plugin a few days back to try and set up a BBI to keep the "full" nettraffic (default) sitting next to some other of my BBI scripts, and it's still a WIP so I haven't fiddled with it much, yet. One time I did and blackbox crashed..ah well.

So I think I'll be able to live with the default version.

Awesome plugin, tho, now I know when my modem lags and I have to restart it...

@a43:
The plugin really doesn't take floating point numbers . I'll change it in the next version.

@qwilk:

So when it's loaded with beginPluginEx the being/not being in the slit should be controled by its own flag/settings and while it's loaded with beginSlitPlugin it should add itself to slit no matter what its own slit settings say?


Oh my god! I totally forgot!

According to qwilk that's how beginPluginEx should work, but none of my plugins do that, I'm evil though see

It is not improper to have it forced into the slit if you ask me, but me and qwilk have agreed to disagree on that Unless qwilk changed xoblite so it try to load everything using beginPluginEx first, in which case I'll have to agree with him.. Damn politicians!

Hmm, with all due respect I do not think we have disagreed on that Tres`ni... have we?

Anyway, the way I see it, yes, when beginPluginEx (which I introduced in xoblite bb1 for this exact reason) is used, the plugin should keep track of its slit status and dock to the slit accordingly. beginSlitPlugin, on the other hand, is (as far I know) only used when the plugin has been &-loaded, i.e. when the user wants to force the plugin into the slit, whereas beginPlugin is used when the plugin has not been &-loaded. The drawback with this approach, however, was that there was an ambiguity about where the user should look for the "dock to slit or not" setting. Should he/she use a config item in the plugin menu or have to manually open plugins.rc (soooo last century! ) and add/remove the & character? Please note that this ambiguity is removed by explicitly requiring that the plugin keeps track of its own slit status when beginPluginEx is used; otherwise it would be no more than a duplicate of beginSlitPlugin.

The entry points are tried in the following order:


http://xoblite.net/source/PluginManager.cpp.html

BR//Karl -> qwilk