|
-
Aug 28th, 2017, 01:21 PM
#1
Re: [vb6]Alpha Image Control v2 - Final Update (15 Jan 2012)
It's a typo in the original stdole2.tlb. How it doesn't crash every time boggles the mind.
OCIdl.idl uses BOOL (32bit) while stdole2.tlb uses VARIANT_BOOL (16bit)
Have you tried invoking SaveAsFile using DispCallFunc() instead?
Last edited by DEXWERX; Aug 28th, 2017 at 03:22 PM.
-
Aug 28th, 2017, 07:23 PM
#2
Addicted Member
Re: [vb6]Alpha Image Control v2 - Final Update (15 Jan 2012)
 Originally Posted by DEXWERX
It's a typo in the original stdole2.tlb. How it doesn't crash every time boggles the mind.
OCIdl.idl uses BOOL (32bit) while stdole2.tlb uses VARIANT_BOOL (16bit)
Have you tried invoking SaveAsFile using DispCallFunc() instead?
DispCallFunc()?? didn't know... but the fix work now, so...
Got a couple of question though...
1. where can we get documentation about OCIdl.idl and stdole2.tlb for the matter at hand ??
2. I saw you did a vb6.tlb, what does it does and would it be possible to create a vb6.tlb to fix and replace stdole2.tlb ?
thanks
-
Aug 29th, 2017, 09:09 AM
#3
Re: [vb6]Alpha Image Control v2 - Final Update (15 Jan 2012)
 Originally Posted by VbNetMatrix
DispCallFunc()?? didn't know... but the fix work now, so...
Got a couple of question though...
1. where can we get documentation about OCIdl.idl and stdole2.tlb for the matter at hand ??
I always read the source, as MSDN documentation can be lacking and is often wrong.
stdole2.tlb can be decompiled to IDL using the OLE-Com Object viewer (which comes with Visual Studio)
OCIdl.idl comes with any of the Windows or Driver Development kits (or visual studio / visual c++)
 Originally Posted by VbNetMatrix
2. I saw you did a vb6.tlb, what does it does and would it be possible to create a vb6.tlb to fix and replace stdole2.tlb ?
thanks
VB6.tlb's main use is to allow easier use of pointers, by aliasing some of the built in runtime functions.
like getting the safearray reference of an array, and read/write access to memory via pointer,
as well as r/w access to the pointers of VB's reference types (string/array/object).
It's also declares often used functions like CopyMemory.
It's possible to correctly VB-Ize the IPicture definition from OCIdl.idl and include it in a typelib like my VB6.lib
That's actually a great idea. I need to finish adding in Control Array interfaces anyway, might as well add a fixed IPicture.
Tags for this Thread
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|