Atl Dll events stop in VB IDE after error triggered 
Author Message
 Atl Dll events stop in VB IDE after error triggered

I have an Atl Com Dll set up as STA with a second thread that posts
messages to the main object of the Dll (this has a hidden Atlwin window)
that handles the messages (with msg map defined). The main object
then fires events (set up as dispinterface) at the appropriate time.
I have a VB client program that runs correctly as a compiled exe, and
the events trigger fine. When the client is running inside the VB Ide
after a few error object operations (with the OnError goto code in
vb app to a msgbox), the events stop. The client will still continue
to respond to keyboard and mouse events, just not mine.
Help?
Rob


Tue, 20 May 2003 03:00:00 GMT  
 
 [ 1 post ] 

 Relevant Pages 

1. ATL COM DLL in VB IDE error...

2. ATL DLL event sink with a VB ActiveX DLL event source

3. ATL - Serious Memory leak triggering events

4. VB Auto-generation of certain events (was Re: VB refuses to load my control DLL)

5. ATL Service - Sporadically does not report SERVICE STOP in event log

6. VB.NET compiler crashes itself or the IDE, when referencing C# DLL

7. BUG: VB.NET compiler crashes itself or the IDE, when referencing C# DLL

8. Passing String Argument from a VB IDE to C DLL

9. VB's mousepointer property not working when set from event of custom ATL control

10. Handling ATL Control events in VB

11. Problem firing an event from ATL to VB which passes a SAFEARRAY

12. COM, ATL, VB, and Events

 

 
Powered by phpBB® Forum Software