RB Smissaert <bartsmissaert@blueyonder.co.uk> schrieb im Beitrag
<OOFrohH1IHA.5564@TK2MSFTNGP06.phx.gbl>...
> long _stdcall ArrayPointer([in] SAFEARRAY(void*)* Array);
This would be a pointer to a SAFEARRAY each element of which is a VOID
pointer!
> long _stdcall ArrayPointer([in] SAFEARRAY(void*) Array);
This would be a SAFEARRAY each element of which is a VOID pointer!
What you seem to need (and what you didn't list as something you have
tried) is a pointer to a SAFEARRAY each element of which is 'a void' (i.e.
any type:
long _stdcall ArrayPointer([in] SAFEARRAY(void)* Array);
Cmp. the sample from VBVM6Lib.tlb which you have provided:
> long __stdcall ArrPtr([in] SAFEARRAY(void) * Ptr);
> But this is something I can't do with the tlb editor and the Pointer level
> box shows empty with the label
> in red, suggesting there is something wrong there. So, is this a bug or a
> limitation in Curland's tlb editor,
> or is there a way to do this without using .idl?
If with that editor an entry like
long _stdcall ArrayPointer([in] SAFEARRAY(void)* Array);
can't be created, it obviously is a problem of the editor since this is
correct IDL syntax (I myself don't know this editor...).

Signature
----------------------------------------------------------------------
Thorsten Albers albers(a)uni-freiburg.de
----------------------------------------------------------------------
RB Smissaert - 22 Jun 2008 19:12 GMT
Thank; so this increases my suspicion that this is a bug in that editor.
I think Matthew Curland has moved away from VB6, so I may have to
look at the source code (which I have) and see if this can be fixed.
RBS
> RB Smissaert <bartsmissaert@blueyonder.co.uk> schrieb im Beitrag
> <OOFrohH1IHA.5564@TK2MSFTNGP06.phx.gbl>...
[quoted text clipped - 27 lines]
> can't be created, it obviously is a problem of the editor since this is
> correct IDL syntax (I myself don't know this editor...).
Thorsten Albers - 22 Jun 2008 20:46 GMT
RB Smissaert <bartsmissaert@blueyonder.co.uk> schrieb im Beitrag
<#W8FQOJ1IHA.5472@TK2MSFTNGP06.phx.gbl>...
> Thank; so this increases my suspicion that this is a bug in that editor.
> I think Matthew Curland has moved away from VB6, so I may have to
> look at the source code (which I have) and see if this can be fixed.
Since you seem to experiment a bit around with type libraries and the VB
runtime maybe this may be of interest for you: With VS 6/VB 6 there is
shipped a tool called OLE/COM Object Viewer (OLEVIEW.EXE) which allows you
to browse the type library within the MSVBVM60.DLL. This allows you to see
the type library entries used by VB.

Signature
----------------------------------------------------------------------
Thorsten Albers albers(a)uni-freiburg.de
----------------------------------------------------------------------
RB Smissaert - 22 Jun 2008 21:06 GMT
Yes, got that one and that is how I could post the .idl.
RBS
> RB Smissaert <bartsmissaert@blueyonder.co.uk> schrieb im Beitrag
> <#W8FQOJ1IHA.5472@TK2MSFTNGP06.phx.gbl>...
[quoted text clipped - 7 lines]
> to browse the type library within the MSVBVM60.DLL. This allows you to see
> the type library entries used by VB.