I failed to mention, that with the newest tcl4bb, I'm 'Not' getting the problems with the font issue mentioned previously. I'm not sure why I'm not having the problem though...

soooo... got any luck on it??? cause I still don't have it running yet.

Working working work.. At work now, I'm always at work

Alright, at work, definately not a "clean" machine but I was able to get tcl-bb working.

I have the runtime and .Net 2.0 installed, apparently no .Net 1.1 *shrug* should work with either.

I did learn that trying to load the plugin with a path like:
C:/Documents and Settings/BrianHartvigsen/Desktop/bblean_116/plugins/tcl-bb/tcl-bb.dll

doesn't not work too well It couldn't find the init.tcl... *shrug* I have the runtimes as installed by Express Editions of C++ and C#. Running XP Pro SP2.

Also tested with the latest BBLean_mod_mod and it worked.. I'll try it on my machine at home tonite or tomorrow. It doesn't have any development tools or anything on it..

tresni - dont suppose you got it working on your new machine at home... did ya?

Actually I just remote desktoped to my machine, and..well... it didn't work... At all..
I've got .Net 1.1 & .Net 2.0, all the nessacary DLL's (as far as I know) and it hates me too.. What sucks is I guarentee as soon as I stick a debugger on there to figure out what's going on it will work fine..

Damn, now I can't remember if I always install something from VS on new machines before I install blackbox and tcl4bb.

btw, I removed .NET2.0 and installed .NET3.0 beta and tcl4bb's still working... just thought I'd report that.

Okay so the error it throws is:
23:05:48 - GetLastError: Invalid access to memory location.

Which really didn't mean anything to me. So I rebuilt tcl-bb in Debug mode and loaded that.. Loads fine on this machine. My guess is that machines that have some form of VS installed are going to be fine, while everyone else is SOL. Something about the Debug build is slowing down the loading of the plugin and allowing it to work on more systems. This is all my guess here, no gospel behind this.

That's all I got right now..

What about that upx compression thing? I think that's what it's called. But some people who couldn't load bbi at one time, could when it was wrapped in that.

You are a genius my friend. It seems the problem was the UPX compaction for me anyway. So, from now on [and here in a few minute I will repost teh build sans UPX] no UPX.. Weird..

Now I really have to be and am going back to bed.. Got woken up by In Laws wanting to leave for home..

I just don't really get what it is about UPX that allows plugins to run when they normally wont. Does it do the slow down thing as with the debugger or something?

ACtually the problem in this case was the UPX Compression. Aparently it wasn't extracting the way it should or was extracting memory that isn't suppose to be or something. When I used an uncompressed dll it worked fine...

All this is is 2.4.8 sans UPX compression. This worked for me on my non-dev system that I was unable to get the plugin to work with prior to this. Please test and let me know!

-- Brian

Here's a question. Can tcl4bb tcl files use pkg definations?

With bbibrowser for example, I tried pkg_mkIndex on it and allthough it indexed the tcl file correctly, tcl4bb did not auto add it to the library.

What would be needed to make custom tcl files indexable? My main goal is to cut down on people having to do the source command and just do package requires in their main tcl4bb.tcl file.

Edit... Nevermind, I think I know how and it would probably be impossible to do it in the way I mentioned above.

BUUUUTTTT.... I'd still like to see either activeTCL's thread.tcl have the ability to access tcl4bb broams or tcl4bb to have some sort of way of handling threading internally. I do think that getting active's working correctly would be a better solution though.
This will come in handy when I start doing internet data retrieval and bbi object assignments. Mainly to prevent tcl4bb hogging blackbox and enabling folks to still use blackbox while tcl is processing it's data.

The only reason I can see threading causing problems is if the thread is created outside of the DLL's space. If it is then that thread is going to be unable to send broams to blackbox and will instead have to use BBKontroller-Proxy and WM_COPYDATA..

That's all I have for now