builtin oleaut32

Medland, Bill Bill.Medland at accpac.com
Tue Jun 11 13:09:23 CDT 2002

> -----Original Message-----
> From: Ann and Jason Edmeades [mailto:us at the-edmeades.demon.co.uk]
> Sent: Tuesday, June 11, 2002 10:20 AM
> To: wine devel
> Subject: builtin oleaut32
> Hello,
> I have been doing some playing with builtin oleaut32 and a 
> Visual Basic
> program I am trying to get working under wine with no-windows 
> (well, as
> little as possible anyway).
> I noticed after copying some ocx files from windows, I was 
> starting to trap
> due to unimplemented stubs inside oleaut32, and have started 
> coding up just
> enough to get my application working. Every time I fix one 
> issue, I find 2
> others, so before I dive in too far has anyone else done any work in
> improving this area which hasnt been submitted, or is anyone actively
> working on this - or should I just continue?

Basically that's what I noted too.  I am sort of working in the area but I
haven't even got everything working natively yet (since I started from a
non-windows installation and it's hard to figure out what needs to be put
in).  I would suggest that the best solution is to submit small packages at
regular intervals.

> Currently I have:
> VarCmp support for BSTR and Integer variants
> VarAnd support for boolean variants only
> VarNot support for boolean variants only
> VarParseNumFromStr support for negative numbers
> VarNumFromParseNum support shorts
> VarDateFromUDate return value is incorrect
> VarNot support for boolean variants only
> Two other questions as I am still fairly new at Unix in 
> general, let alone
> wine....
> 1. What is the policy on patches - Is one big one with all 
> changes for the
> same module ok?
> 2. What about tracing - While writing them I have added trace 
> to show the
> parms and return values (relay just shows the rc whereas the 
> actual return
> value is normally a third varient). Should I leave these in?

Sounds a good idea.  Presumably they are under the ole debug channel.  If it
gets ridiculous it might be worth adding a new debug channel.

> Thanks
> Jason


More information about the wine-devel mailing list