#Lost Sub labels
3 messages in this thread
Hi Ricks,
I don't know of any resource that are lost by VB. Also, if VB is given a
handle to a bitmap, it wouldn't delete the resource that is maintain/created
in a DLL. It would not be the responsibility of VB to do this. It is
calling the DLL, it doesn't know what the DLL wants to do with this. If you
are passing a hBitMap handle to VB, this handle would be put into the
picture1.picture property and used.
Don Funk
There are 2 Replies.
This is a bug (one of many) in VB – the stupid environment loses
track of its labels when operating in immediate mode when the
labels are located in the general section of another module. Running
and rerunning the application does not elimiate the problem, only dumping
the project and reloading it.
This is a BUG in VB – this is not a feature – there is nothing unusual I am
doing in the environment, and I am not the only one with the problem. So,
Microsoft, when are you going to admit the problem and release a fix for
it?
I thought that all memory allocated by a DLL (including Resources) were owned
by the calling program – Not the DLL, since the DLL would never know when the
resources were finished. (Turbo Pascal stops it's Global Memory
suballocation scheme when a DLL is executing so the application gets a
complete memory block.) I now think my problem rears it's head while *in*
VB, not with the compiled programs.
– Ricks