Re: activex as ui for com
- From: "Alexander Nickolov" <agnickolov@xxxxxxxx>
- Date: Fri, 18 Nov 2005 13:37:39 -0800
I suppose you actually need an ActiveX Control (it's hard to tell
from your somewhat garbled post...). A rule of thumb to remember
is that messages should not be used together with COM method
calls, e.g. your protoicol should not mix COM with messages.
Using Windows messages as part of the implementation of a
COM object is perfectly fine, however, since it does not affect
its clients.
--
=====================================
Alexander Nickolov
Microsoft MVP [VC], MCSD
email: agnickolov@xxxxxxxx
MVP VC FAQ: http://www.mvps.org/vcfaq
=====================================
"alojzy" <all@xxxxxxxxx> wrote in message
news:%23ENc5AA7FHA.2524@xxxxxxxxxxxxxxxxxxxxxxx
> Hello,
> I need to create simple activex as a user interface for some COM
> component.
> What would be the most proper way, It would be nice to send just messages,
> can COM hadle messages when it doesn't have window? Or I have to create
> sink?
> COM is inprocess.
> thanks
>
.
- Follow-Ups:
- Re: activex as ui for com
- From: alojzy
- Re: activex as ui for com
- References:
- activex as ui for com
- From: alojzy
- activex as ui for com
- Prev by Date: Re: Multiple IDispatchImpl-Inheritance?
- Next by Date: Re: VS2k3=>VS2k5 == LNK2005 on g_pfnGetThreadACP
- Previous by thread: activex as ui for com
- Next by thread: Re: activex as ui for com
- Index(es):
Relevant Pages
|
Loading