Re: generated stubs fail to compile

Hi Ed,

Yes these failures do make sense...

Basically the MS type lib system allows for a gazillion type mappings, each
requiring some sort of special handling to map these to jawin code.

The native side of the parser, written in C++ and used by the type browser,
loads the type library and tries to generate an intermediate XML file, which
the type browser styles using XSLT into java wrapper code.

The failure you are seeing is occurring in the type parser, the java code
that interfaces with the native code:

http://jawinproject.cvs.sourceforge.net/jawinproject/jawin/src/org/jawin/browser/typelib/TypeParser.java?view=markup

I think this code still needs some tidying up...

Basically the issue you are seeing is that when the native type info is
coming back its matched up to type configuration which details how the jawin
conversion should occur and this is stored in this file:

http://jawinproject.cvs.sourceforge.net/jawinproject/jawin/config/typeconversion.xml?view=markup

As you can see, typeconversion.xml has holes for the types you are trying to
map: 6, 10 and 28

I'm not sure exactly what these types are or why we didn't map them, its not
very hard to add the mappings once you know what the code should look like
on the jawin side.

Anyone know what these types are and how they should be mapped?

Josh


>
>Hi Josh,
>
>   Do these failures make any sense to you?
>
>Thanks,
>Ed
>
>[DEBUG] ********************************************
>[DEBUG] TypeInfo GUID: GUID{91493440 5a91 11cf 00 00 00 00 00 00 00 00
>}
>[DEBUG] TypeInfo Locale: 0
>[DEBUG] TypeInfo Platform: 1
>[DEBUG] TypeInfo Major version: 2
>[DEBUG] TypeInfo Minor version: 8
>[DEBUG] TypeInfo Flags: 8
>[DEBUG] ********************************************
>[DEBUG] TypeInfo GUID: GUID{2df8d04c 5bfa 101b 00 00 00 00 00 00 00 00
>}
>[DEBUG] TypeInfo Locale: 0
>[DEBUG] TypeInfo Platform: 1
>[DEBUG] TypeInfo Major version: 2
>[DEBUG] TypeInfo Minor version: 3
>[DEBUG] TypeInfo Flags: 8
>[DEBUG] ********************************************
>[DEBUG] TypeInfo GUID: GUID{0002e157 0000 0000 00 00 00 00 00 00 00 00
>}
>[DEBUG] TypeInfo Locale: 0
>[DEBUG] TypeInfo Platform: 1
>[DEBUG] TypeInfo Major version: 5
>[DEBUG] TypeInfo Minor version: 3
>[DEBUG] TypeInfo Flags: 8
>[DEBUG] ********************************************
>[DEBUG] TypeInfo GUID: GUID{00020430 0000 0000 00 00 00 00 00 00 00 00
>}
>[DEBUG] TypeInfo Locale: 0
>[DEBUG] TypeInfo Platform: 1
>[DEBUG] TypeInfo Major version: 2
>[DEBUG] TypeInfo Minor version: 0
>[DEBUG] TypeInfo Flags: 8
>[DEBUG] TypeParser.buildTypeDescription() failed to find a configured type
>for property: Data4 with type code: 28
>[DEBUG] TypeParser.buildTypeDescription() failed to find a configured type
>for property: scode with type code: 10
>[DEBUG] TypeParser.buildTypeDescription() failed to find a configured type
>for alias: FONTSIZE with type code: 6
>TypeParser.buildTypeDescription() the pointer property with type = 6 is not
>implemented yet
>Size - unknown VT-type (6) at psize 1th parameter
>[DEBUG] TypeParser.buildTypeDescription() failed to find a configured type
>for property: Size with type code: 6
>
>Josh Passenger <[email protected]> wrote: Hi Ed,
>
>Can you post the native signature you are trying to generate stubs for?
>
>Josh
>
> >
> >If a member has a void type, is it safe to replace the void with Object
>via
> >the xsl?
> >
> >   Thanks,
> >   Ed
> >
> >Florian Schmitt  wrote:
> >   Hi Keith,
> >
> > > I have a similar problem with the stub generator and the PowerPoint
>OLB
> > > MSPPT.OLB. I have many methods in the _Application class, however
>there
> > > are many undefined symbols:
> > >
> > > Script
> > > WebPageFonts
> > > CommandBars
> > > Assistant
> > > FileSearch
> > > IFind
> > > VBE
> > > AnswerWizard
> > > COMAddIns
> > > LanguageSettings
> > > MsoDebugOptions
> > > FileDialog
> > > NewFile
> >
> >I suppose that some or all of them are defined in other libraries; for
> >example, Script and Assistant can be found in MSO.dll (MS Office Objekt
> >Library), which may be located under Program Files\Common Files\Microsoft
> >Shared\OfficeXX, where XX has to be replaced by your MS Office version
>(eg.
> >Office10).
> >
> >Another library which may be of interest are VBE6EXT.OLB under Program
> >Files\Common Files\Microsoft Shared\VBA\VBA6; there's 'VBE' as Dispatch
> >located, for example.
> >
> >A good way to find those files is using the References Dialog provided by
> >the Visual Basic Editor. It shows for every reference to a library the
>path
> >to the library file. So it's easy to collect all libraries needed as one
> >would do for an VBA project.
> >
> >
> >Florian
> >
> >--
> >http://www.florian-schmitt.net
> >
> >
> >
> >>
> >---------------------------------
> >Talk is cheap. Use Yahoo! Messenger to make PC-to-Phone calls.  Great
>rates
> >starting at 1¢/min.
>
>
>
><!--
>
>---------------------------------
>Stay in the know. Pulse on the new Yahoo.com.  Check it out.