wine-devel

wine-devel@winehq.org

2 participants
84479 discussions

Re: [help] GDI text fonts
by Huw D M Davies 03 Jul '02

03 Jul '02

On Wed, Jul 03, 2002 at 04:54:18PM +0800, leanne wrote: > Huw D M Davies wrote: > > > > >It's still not clear to me whether you're using XServer rendered fonts > >or client side (Wine) rendered fonts. Could you send me the > >--debugmsg +font,+xrender log ? > > > >Huw. > > > Hello, > > I have checked cvs today and found that it supports to download tt > fonts to printer but the position of the text messes up. > Maybe it's a bug. > > I still find the font of the interface is very ugly, what do you think? > Attached please find the log and screenshot. > Very thanks. > > trace:font:DumpFontList Family: L"AR PL Mingti2L Big5" > trace:font:DumpFontList L"Reguler" > trace:font:DumpFontList Family: L"AR PL KaitiM Big5" > trace:font:DumpFontList L"Regular" There's a problem with Type42 font downloads, a workaround for this to edit generic.ppd and change the line *TTRasterizer: Type42 to *TTRasterizer: None this will tell Wine to send download the font as a Type 1 outline which should work. Do you mean that the roman (English) font is ugly (since I have no idea whether the Chinese characters look ok maybe you let me know how they look)? You only have two fonts installed (see the above fragment from the log), so the english text has to come from one of these fonts. What you may want to do is to install some fonts like Arial, Times New Roman etc. You could either copy these from a Windows installation (or add a line to the [FontDirs] section of config to point at an existing Windows partition font directory), or you can download a selection of the core Windows fonts from Microsoft's website. Huw. -- Huw Davies huw(a)codeweavers.com

1 0

Still getting this error
by Steven Edwards 03 Jul '02

03 Jul '02

With the last release I can build and use wine but with the current CVS I still get the following errors. Warning: loading builtin gdi32.dll, but native version already present. Expect trouble. Warning: loading builtin user32.dll, but native version already present. Expect trouble. wine: Unhandled exception, starting debugger... I am still not able to track down the patch that causes this. I have a clean WINE with no windows on any of my drives in my slackware box. Thanks Steven __________________________________________________ Do You Yahoo!? Yahoo! - Official partner of 2002 FIFA World Cup http://fifaworldcup.yahoo.com

1 1

Re: Private Profile Regression Test
by Dmitry Timoshkov 03 Jul '02

03 Jul '02

"Joshua Thielen" <thielen(a)netprince.net> wrote: > Anyhoo, please let me know what you think - are the tests sufficient, > too much, not written properly? etc. First of all, thank you very much Joshua! Really great work! A couple of comments though: /* * Special case: NULL lpReturnedString with size > 0 * This causes an application error in win2k. Let's make wine better :) */ IMO it's not very good idea to make some tests succeed under Wine, which clearly crashes under win2k. That would play some bad role in the case of the back porting Wine code to Windows, since some code, internal to Wine, could rely on that forbidden API behaviour. I also have the following failures under win2k: Number of bytes read do not match FAIL: c:\result.ini does not match compare1.ini Number of bytes read do not match FAIL: c:\result.ini does not match compare2.ini -- Dmitry.

2 2

Re: Small 'let's prevent a crash' fix
by Lionel Ulmer 02 Jul '02

02 Jul '02

> This does not fix the real problem (ie why does this DC not have a font even > if the application called a 'SelectObject' on it), but well, it cannot harm > to be more verbose and to prevent crashes if possible :-) OK, found the 'error' : the problem comes from the fact that I am using client-side fonts (aka XRender) : so the 'font' part of the physDev structure is always '0'. And that also means that we cannot use as is the glXUseXFont function. So basically, I need to implement it myself using 'GetGlyphOutline' (should not be that hard to do :-) ). Now my question : is 'GetGlyphOutline' always working even when not using client-side fonts ? If yes, I will completely remove the call to glXUseXFonts (I know, in that case, fonts displayed by OpenGL will be different by the one displayed by X, but well, ...) and always use the manual 'GetGlyphOutline' function. And I will try at the same time to remove all GLX calls from wgl.c and put them in special X11DRV escapes to have a real X11 free wgl.c file (ie for example, creating an OpenGL context would be a special escape for the X11DRV as it's basically something that is in GLX). Lionel -- Lionel Ulmer - http://www.bbrox.org/

2 1

Re: Removed extra , from enum declarations
by Andreas Mohr 02 Jul '02

02 Jul '02

On Tue, Jul 02, 2002 at 03:39:04PM -0400, Gregg Mattinson wrote: > Resubmitting because I forgot to attach the file. Sorry. I'm also sorry about > the large number of posts today. You feel sorry about WHAT !? Heck, I guess you might have a minimalistic reason to feel sorry once you manage to crash the mailing list server due to sending way too many patches, but until that happens... ;-) Have a nice day ! -- "My attitude is, everybody should try competing with Microsoft once in their life. Once." - Marc Andreessen, former Netscape lead employee, in a "browser wars" interview

1 0

Re: Added support for APPMODE=<type>[:<mainFunc>]
by Joerg Mayer 02 Jul '02

02 Jul '02

On Tue, Jul 02, 2002 at 04:06:56PM -0400, Gregg Mattinson wrote: > - .spec files can't be compiled with -g when using Forte C. This causes static > variables to have a "random" prefix attached to their name, and prevents the > assembly code from linking to them correctly. > - Forte C has linker issues, so cui executables with main() conflicted with > main() in $WINELOADER. Renaming main() to main2() solved the issue, so I added > support to winebuild to allow the main function name to be optionally specified > in the makefile. > - Forte C does not support .previous It was replaced with a .section statement > for the appropriate section > - '.section .text' is incorrect. It should be '.section ".text"' You omitted: - Replace constants by numeric values (aka magic numbers). > - fprintf( outfile, " rec.code = 0x%08x;\n", EXCEPTION_WINE_STUB ); > + fprintf( outfile, " rec.code = 0x%08x;\n", 0x80000100 ); - Inserted compiler specific compilation (as opposed to feature specific compilation) > +#ifndef __SUNPRO_C > fprintf( outfile, "\n#include \"pshpack1.h\"\n" ); > +#endif - Removed some unneeded includes. Ciao Jörg -- Joerg Mayer <jmayer(a)loplof.de> I found out that "pro" means "instead of" (as in proconsul). Now I know what proactive means.

1 0

Re: Void functions can't return a value
by Joerg Mayer 02 Jul '02

02 Jul '02

On Tue, Jul 02, 2002 at 03:34:44PM -0400, Gregg Mattinson wrote: > - void functions can't return a value, even if it is the return value from > another void function. Just looking at the patch a bit. This looks wrong to me. If you want to make the changes, you should convert return xxx() into { xxx(); return } > void WINAPI PathStripPathAW(LPVOID lpszPath) > { > if (SHELL_OsIsUnicode()) > - return PathStripPathW(lpszPath); > - return PathStripPathA(lpszPath); > + PathStripPathW(lpszPath); > + PathStripPathA(lpszPath); <----- should not be executed if condition is met > } This pattern is repeated several times. Ciao Jörg -- Joerg Mayer <jmayer(a)loplof.de> I found out that "pro" means "instead of" (as in proconsul). Now I know what proactive means.

1 0

Re: heads up: wine 20020605 broken on FreeBSD, workaround included
by Gerald Pfeifer 02 Jul '02

02 Jul '02

[ I'm now also Cc:ing this to the Wine developers, thus the full-quote. In fact, all non-GLIBC platforms seem to be affected by this bug! ] Based on your pointer, I believe I found the problem. In aclocal.m4 we have: AC_DEFUN([WINE_CHECK_ERRNO], [AC_CACHE_CHECK([for reentrant libc: $1],[wine_cv_libc_r_$1], [AC_TRY_RUN([int myerrno = 0; char buf[256]; int *$1(){return &myerrno;} main(){connect(0,buf,255); exit(!myerrno);}], wine_cv_libc_r_$1=yes, wine_cv_libc_r_$1=no, wine_cv_libc_r_$1=yes)]) AS_IF([test "$wine_cv_libc_r_$1" = "yes"],[$2],[$3])]) which, in configure, becomes: int myerrno = 0; char buf256; int *__error(){return &myerrno;} main(){connect(0,buf,255); exit(!myerrno);} That is, instead of an array of 256 characters, we have one character, and the invocation of connect() is definitely incorrect. Could someone more familiar with autoconf please have a look at this? Gerald On Mon, 1 Jul 2002, Scott Bolte wrote: > Over the weekend I tried to get wine 20020605 to run on a > new installation of FreeBSD 4.6. It took a while, I haven't > tried wine since 1997 after all, but I determined that my > problems were due to configure's reentrant libc test failing > when building the port. > > The wine_cv_libc_reentrant test in configure.ac first checks > for Linux (__errno_location) and then tests for FreeBSD > (__error). I don't have more time to figure out why, but > nesting the FreeBSD test that way results in a false > negative. The configuration will continue, as will the > build, but the resulting non-reentrant code goes into an > endless loop when trying to spawn threads. > > A crude workaround, for FreeBSD users at least, is to > replace the Linux test with the FreeBSD one. This needs to > be done before configure is run. I did it by hand, but I > expect the following code would do the trick. > > % cd /usr/ports/emulators/wine > % make patch > % perl -i -pe 's/__errno_location/__error/' work/wine-20020605/configure.ac > % make > % make install > > Below is the autoconf test script that demonstrates the > problem. It needs to be run in > /usr/ports/emulators/wine/work/wine-20020605/configure.ac > > Scott > > P.S. I'm not on the freebsd-emulators mailing list, but I > see from freebsd-questions that at least one other > person got wine to compile on 4.6. I can't explain > why it worked for him and not for me. However, I > installed a brand new copy of 4.6 from the standard > ISO images just to run wine. > > ---- testconf.ac > dnl Process this file with autoconf to produce a configure script. > dnl Original author: Michael Patra > dnl See ChangeLog file for detailed change history. > > m4_define(WINE_VERSION,regexp(m4_include(VERSION),[version $[-.0-9A-Za-z]+$],[\1])) > > AC_PREREQ(2.53) > AC_INIT([Wine],WINE_VERSION) > AC_CONFIG_SRCDIR(server/atom.c) > AC_CONFIG_AUX_DIR(tools) > > dnl **** Check for some programs **** > > AC_PROG_CC > > dnl **** Check for reentrant libc **** > > wine_cv_libc_reentrant=no > > dnl ##### > dnl ##### There is a problem if the FreeBSD test is nested > dnl ##### after the Linux test. In that instance, it fails. > dnl ##### If, on the other hand, it is tested first, it works. > dnl ##### > dnl ##### Swap the order of two following test case to see > dnl ##### how they differ. (Ignore the second case since it > dnl ##### will use cached data.) > dnl ##### > > dnl FreeBSD style errno location > WINE_CHECK_ERRNO([__error], [wine_cv_libc_reentrant=__error]) > > dnl Linux style errno location > WINE_CHECK_ERRNO([__errno_location], [wine_cv_libc_reentrant=__errno_location], > dnl FreeBSD style errno location > WINE_CHECK_ERRNO([__error], [wine_cv_libc_reentrant=__error] > )) > -- Gerald "Jerry" pfeifer(a)dbai.tuwien.ac.at http://www.dbai.tuwien.ac.at/~pfeifer/

3 4

alsa disable configure?
by Chris Thielen 02 Jul '02

02 Jul '02

Are there any patches in waiting to disable the use of ALSA in the configure script ... or is this not needed?

1 0

IsDialogMessageA/W question
by Sander van Leeuwen 01 Jul '02

01 Jul '02

Hi, Is there a specific reason why unprocessed messages in IsDialogMessage don't get dispatched? Experiments in Windows 2000 show this is not (always) correct. It seems all messages passed on to IsDialogMessage are dispatched and it always returns 1. IsDialogMessage doesn't call DispatchMessage, but the function called internally by DispatchMessage. Changing the behaviour to match Windows 2000 fixes at least one problem I noticed in an MFC application (button getting stuck when using the spacebar). There's not much information in MSDN about this function, so I can't say if IsDialogMessage always behaves like this. Sander

3 2

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-devel