Fontforge and building wine

2007-11-25 Thread Dan Kegel
It's been mentioned many times, but building Wine without a recent fontforge yields a wine that doesn't work too well. Tonight, for instance, I built wine on an updated dapper system, and forgot; here are the commands I had to use to recover (just in case somebody needs to do this again). The font

1.0 bugs

2007-11-25 Thread Dan Kegel
[putting on tastemaster hat] So far, 82 bugs have been nominated to be fixed for 1.0. I checked a bunch of them, and so far most look reasonable. Some even look easy or have patches, e.g. http://bugs.winehq.org/show_bug.cgi?id=5402 http://bugs.winehq.org/show_bug.cgi?id=5884 http://bugs.winehq.or

Re: wined3d: Bind device framebuffer in ActivateContext

2007-11-25 Thread Allan Tong
> The framebuffer setup should be merged with ActivateContext, but not by simply > setting the framebuffer to 0. Currently there are two issues: the one you are > seeing(the complaints from opengl), and multithreading issues. > > Parts of the code call ActivateContext before setting the fbo: In thi

Re: shdocvw: Silence common invalid QueryInterface FIXMEs.

2007-11-25 Thread Alistair Leslie-Hughes
> hres = IUnknown_QueryInterface(unk, &IID_IRunnableObject, > (void**)&runnable); > ok(hres == E_NOINTERFACE, "QueryInterface returned %08x, expected > E_NOINTERFACE\n", hres); > ok(runnable == NULL, "runnable=%p, ezpected NULL\n", runnable); > + > +hres = IUnknown_QueryInterface(

Re: wined3d: Bind device framebuffer in ActivateContext

2007-11-25 Thread Stefan Dösinger
Am Sonntag, 25. November 2007 20:26:21 schrieb Roderick Colenbrander: > Also don't forget that a lot of function calls (especially in surface.c) > still mess with glDrawBuffer themselves. For a lot of calls this is > redundant. Yes, most of them should be removed now that ActivateContext takes car

Re: wined3d: Bind device framebuffer in ActivateContext

2007-11-25 Thread Roderick Colenbrander
> > On Nov 25, 2007 7:15 AM, Stefan Dösinger <[EMAIL PROTECTED]> > wrote: > > > Am Sonntag, 25. November 2007 00:07:15 schrieb Allan Tong: > > > > Fixes failures in visual tests for ddraw and d3d8 when using FBO > > > > offscreen rendering mode. > > > > > > > > - Allan > > > > > > This doesn't loo

Re: wined3d: Bind device framebuffer in ActivateContext

2007-11-25 Thread Stefan Dösinger
Am Sonntag, 25. November 2007 18:13:43 schrieb Allan Tong: > On Nov 25, 2007 7:15 AM, Stefan Dösinger <[EMAIL PROTECTED]> wrote: > > Am Sonntag, 25. November 2007 00:07:15 schrieb Allan Tong: > > > Fixes failures in visual tests for ddraw and d3d8 when using FBO > > > offscreen rendering mode. > >

Re: wined3d: Bind device framebuffer in ActivateContext

2007-11-25 Thread Allan Tong
On Nov 25, 2007 7:15 AM, Stefan Dösinger <[EMAIL PROTECTED]> wrote: > Am Sonntag, 25. November 2007 00:07:15 schrieb Allan Tong: > > Fixes failures in visual tests for ddraw and d3d8 when using FBO > > offscreen rendering mode. > > > > - Allan > This doesn't look right to me. It will most likely b

Re: bug fix: Prevented strlen(NULL) in PRINTDLG_CreateDevNames()

2007-11-25 Thread Stefan Dösinger
Am Sonntag, 25. November 2007 12:35:36 schrieb Jorma Laaksonen: > Hello! > > wine-0.9.49 (as well as many earlier versions) seems to crash when > PRINTDLG_CreateDevNames() is for some reason called with DeviceDriverName > equal to NULL. The real cause of this problem might be somewhere else > wher

Re: wined3d: Bind device framebuffer in ActivateContext

2007-11-25 Thread Stefan Dösinger
Am Sonntag, 25. November 2007 00:07:15 schrieb Allan Tong: > Fixes failures in visual tests for ddraw and d3d8 when using FBO > offscreen rendering mode. > > - Allan This doesn't look right to me. It will most likely break overall FBO support. There is indeed a problem with the fbo and ActivateCo