> Yes, that makes sense - but trying to use it would not crash in > itself, it's just not a very sensible thing to do, correct?
No, since handles are just "handles" it won't result in a crash, but many bugs are better replaced by a crash. Suppose a program writing to your MBR, and you don't have a Linux rescue disc handy. Would you prefer it to crash or corrupt the MBR? :-) > I understand, but I meant: what if I pass a HANDLE across (so using > the passing mechanism correctly) - can I use this HANDLE safely in the > OCX code, or am I in a different process now? I'm not sure if a HANDLE > is one of the automation types, but this is theoretical here. > > Your answer above appears to suggest it should be safe... In general it shouldn't, but in ActiveX controls, it works, albeit you're supposed to be using something like IOleWindow to do it. That is why I suspect ActiveX's can only be inproc. Of course, I'm assuming you don't want to do something other than sending a message to it, or maybe reading a property. I bet you agree that painting a window in that manner from your ActiveX control is a silly idea! BTW, OCX is just an extension (an abomination that VB created!) like any other: DLL, EXE, JPG, etc. ------------- Ehsan Akhgari Farda Technology (http://www.farda-tech.com/) List Owner: [email protected] [ Email: [EMAIL PROTECTED] ] [ WWW: http://www.beginthread.com/Ehsan ] They have something of which they are proud. What do they call it, that which makes them proud? Culture, they call it; it distinguishes them from the goatherds. -Thus Spoke Zarathustra, F. W. Nietzsche _______________________________________________ msvc mailing list [email protected] See http://beginthread.com/mailman/listinfo/msvc_beginthread.com for subscription changes, and list archive.
