Re: Making builtin OLE32 work right

2005-02-19 Thread Mike Hearn
Here is a brain dump of what I already know we need to fix for the CW supported apps: 1) InstallShield:RPC call re-entrancy 2) Lotus Notes: OLE drag/drop leaves an image of the window behind when it closes. Native does this functionality very dif

Re: Making builtin OLE32 work right

2005-02-19 Thread Mike McCormack
Holly Bostick wrote: Now, from what I hear, it's going to become much more difficult for me to do even that in the near future, which stinks, as it was already a PITA. Right. Microsoft will help Wine by making it harder to download parts of Windows, and better to use Wine code. We need to mak

Re: Making builtin OLE32 work right

2005-02-19 Thread Holly Bostick
Mike McCormack wrote: I'm a bit worried that our users are content to use native Windows dlls, which doesn't help achieve Wine's goals. Well, for what it's worth, I certainly am not (content to use native Windows dlls). Today I just tested an app (see "Pretty Good Solitaire shootout" thread), a

Re: Making builtin OLE32 work right

2005-02-19 Thread Mike McCormack
Tony Lambregts wrote: Well If I can get around to submitting my "new bugzilla integration" patch this could work right. The idea is to be able to attach multiple apps (versions) to the same bug. Right now we use "url" in Bugzilla to attach a bug to an app and that limits us to on app per bug. Ye

Re: Making builtin OLE32 work right

2005-02-18 Thread Tony Lambregts
Mike McCormack wrote: Hi All, I'd like to compile a list of all applications that don't work correctly without native ole32 (aka dcom95), then go through and try fix them. I think bugzilla is probably the right place to save the list, and that alot of the information we're looking for is already