VB6 - multi-threading?

[Killer42]

Hi all.

I've only discovered "thescripts" recently, and just realised it's probably the ideal place to ask a question that has been in the back of my mind for a few years now.

I have an old application I was writing some years back (on hold for some time now), which involves running through a bunch of image files, loading them each into a picture box. Every now and then the picture box hits one it can't display, and locks up. This is out of my control (the images can be from anywhere), and since it's the picture box object having problems I can't trap it. There's no error, it simply stops responding.

Is there any way I can have some code in a separate thread watching for this, and somehow kill off the dead thread and start it again? Even if it could just stop the program, or show a warning dialogue, or even just beep or something, that would be an improvement over simply freezing.

[Killer42]

So, apparently nobody knows an answer to this one?

[Killer42]

Still no thoughts on this, anyone?

[Esmael]

HI SIR...

Can u pls... show your codes... maybe i can give you some advice/answer.


Thnx...

[Killer42]

HI SIR...
Can u pls... show your codes... maybe i can give you some advice/answer.

Sorry, it's not really feasible to post the code in this case. It's way too involved, plus it's an old project which is archived somewhere - I'll need to dig around though old disks to find it.

Besides, there isn't any particular code which has a problem. The problem arises when the program simply uses LoadPicture to load images into a picturebox one by one. There are certain images which just kill the PictureBox control, whenever they are loaded into it.

I was just fishing for any sort of ideas on how such a thing might be achieved in VB. I'm beginning to suspect that it can't be done in VB6.

The best idea I've come up with so far is to run a separate program and have them talk to one another somehow, such as DDE. Then hopefully the "watchman" can cancel the main app if it stops responding for a set time. Maybe even start another copy to continue the process. As it stands, the program records a flag saying which image it is about to process. When it starts up, if it finds that flag, it marks that image as one to be avoided and doesn't try to load it. That way I can just can the program and run it again. What I'm hoping for is a way to automate (or avoid) this.

One of these days I'll get back to this program, but it's not really urgent.

Actually, now that I think about it, the need may even have ceased to exist. Given that a few years have passed, the latest version of the PictureBox control may no longer have the lock-up problem.

[Esmael]

Hi...SIR

I see. But i never encounter that problem sir... because i'ved never experience that with the LoadPicture.... i even try it to VB Form Icons..etc.... and it works well.... I not sure if it has something to do with the VB Service Pack...


Have a nice day....