Login
Templates, Tools and Utilities
for Clarion Developers
Templates, Tools and Utilities
|
||
|
|
|
Add a comment to an Icetips ArticlePlease add your comments to this article.
Please note that you must provide both a name and a valid email address in order
for us to publish your comment. Comments are moderated and are not visible until they have been approved. Spam is never approved!
Back to article list Search Articles Add Comment Printer friendly Direct link COM: Example 3 2004-01-15 -- Andy Ireland Newsgroups: softvelocity.public.clarion6
(In response to Carl Barnes)
Hi Carl,
> Thanks for the quick reply. No time today but will review it closely tomorrow.
>
> Your classes don't have IShellLink but have IShellLinkDual. I prefer to stay
> away from the extra complexity of variants in IDispatch interfaces.
IShellLinkDual is the same as IShellLink. That came from my shell32.dll.
Although my OS is a little strange and is in need of reinstalling. Dual
means it's a dual interface i.e early bound rather than a dispatch interface
which is otherwise known as an automation interface which is late bound via
IDispatch.
> The OleInitialize you refer to I think you found in Alexey's original code? He
> named a method OLEInit.Construct even though it called CoInitialize. And he
> also named IUnknown as IOLE which was a little odd. With some name changes its
> a great little COM example.
No you had that as a comment.
> What is a LPCOLESTR? Alexey uses a BSTRING so I just left it that way. E.g.
> IPersistFile::Save
> HRESULT Save(
> LPCOLESTR pszFileName,
> BOOL fRemember
> );
They are the same thing.
Regards
Andy
Today is April 30, 2024, 2:09 pm This article has been viewed 35117 times. Google search has resulted in 14 hits on this article since January 25, 2004.
|
|