Hi! I have developed a simple COM object using ATL 3.0. I intend to use this object in a web page. Everything works nice except for the event firing. These events are being fired from a second thread via a PostMessage mechanism, so that no apartment issues arise. The strange thing is that my ProxyGenerator wizard generated code has the connections variable (int nConnections = m_vec.GetSize();) set to zero (watched this behaviour while debugging) so that the firing doesn't take place. The same thing happens if i package my component has a Lite control. But it all works perfectly fine with a Full control. The problem is that i don't need a UI, consequently, i don't need a Full control's overhead. Is it possible for a simple Com object to Fire Events to the IE? How? Please help me! Thanks in advance. Luís Teixeira
Luis Teixeira
Posts
-
Can't fire events to IE -
Safe for scripting/initializationSo you're saying that you wouldn't mark the control as safe if it is using DirectX. But this control needs to access the sound card for data. I guess that using the multimedia functions of the WIN32 API has the same problem than DirectX, which leaves me no chance to make it a safe control. Thanks so much, Alex! Luís Teixeira
-
Safe for scripting/initializationHi Everybody! I have developed an activeX control that instantiates a "in proc server" which accesses the sound card using DirectX. Neither the control nor the data component (collected from the sound card) write to any files in the user HD. I intend to deploy this control on the internet, so my question is: Can i mark this control and the component as safe for scripting/Initialization? On which conditions can i mark a control with these categories? Thanks in advance, Luís Teixeira