Re: C++ DLL Side Of a VB Call-back function Problem
- From: "Thorsten Albers" <albersRE@xxxxxxxxxxxxxxxxxxx>
- Date: Mon, 20 Nov 2006 15:13:41 -0800
Nate, Nano <nanonut@xxxxxxxxx> schrieb im Beitrag
<1164063170.773039.311090@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>...
I've just completed another part of my troubleshooting and I've
found that when I implement a call to a C++ DLL which calls back a VB
function right away, that the whole system works correctly. However,
when I try to pass the address of a VB call back function, and a C++
DLL thread tries to execute the VB function at a later time (meaning
not within the same function call) that the whole program hangs. Is the
VB call back function being destroyed after the function call? Is there
anyway I can prevent this hanging from happening
The VB function isn't destroyed if it is a regular function within the VB
executable. Note: When a VB application gets started, the executable image
file is mapped to the virtual memory and stays mapped as long as the
application is running. No function which resides in the executable image
will change its virtual memory address for the whole time the image is
mapped to the virtual memory.
Presumably there are other errors in your code which we can't discuss
without seeing the code.
--
----------------------------------------------------------------------
THORSTEN ALBERS Universität Freiburg
albers@
uni-freiburg.de
----------------------------------------------------------------------
.
- References:
- C++ DLL Side Of a VB Call-back function Problem
- From: Nate, Nano
- Re: C++ DLL Side Of a VB Call-back function Problem
- From: Nate, Nano
- C++ DLL Side Of a VB Call-back function Problem
- Prev by Date: Re: Where did my VB function go?
- Next by Date: Re: C++ DLL Side Of a VB Call-back function Problem
- Previous by thread: Re: C++ DLL Side Of a VB Call-back function Problem
- Next by thread: Re: C++ DLL Side Of a VB Call-back function Problem
- Index(es):
Relevant Pages
|