wine-devel

wine-devel@winehq.org

9 participants
84397 discussions

Problem with tooltips
by Marcus Meissner 13 May '01

13 May '01

Hi, Start any program that uses the common dialog file open dialog (Win95 style) using -managed. Then move the mouse over any of the toolbar icons. Watch a VERY HUGE window manager window pop up displaying the tooltip text in the upper left corner. Reason for this appears to be some changed flags that lets WIN_WindowNeedsWMBorder fail on tooltips. Does anyone know how to fix this? Adding WS_EX_TOOLWINDOW to the tooltip CreateWindow is probably wrong :/ Ciao, Marcus

1 0

RE: WINEPS: Read metrics from TrueType fonts
by Nerijus Baliunas 13 May '01

13 May '01

> This patch enables the PostScript driver to read font metrics directly > from TrueType font files with FreeType 2. It looks for font files in > directories listed in the [TrueType Font Directories] section of the > wine config file. For example: > > [TrueType Font Directories] > "dir0" = "/usr/X11R6/lib/X11/fonts/TrueType" > "dir1" = "/usr/share/fonts/default/TrueType" > etc. > > It does not embed the fonts into its output. Ghostscript users can > install their TrueType fonts in Ghostscript (with their Fontmap file or > the GS_FONTPATH environment variable); users printing to PostScript > printers will have to convert their fonts to Type 1 or Type 42 format > and use an external program to add them to the print jobs. Hello, Why don't you add this text to documentation/printing? Regards, Nerijus

1 0

Wine logo
by Ian Pilcher 12 May '01

12 May '01

Inspiration for the graphically (and accurately) inclined: http://www.sutterhome.com/interactive/in1034.html -- ======================================================================== Ian Pilcher ian.pilcher(a)home.com ========================================================================

1 0

Missing INT21h functions
by davep 12 May '01

12 May '01

Trying (more in hope than expectation) to run an ancient DOS program under Wine, I get this failure: err:int21:DOS3Call int21: unknown/not implemented parameters: int21: AX 0f9f, BX 005c, CX 0000, DX 005c, SI 008e, DI 005c, DS 107f, ES 109f Sure enough, DOS3Call() has a series of functions, including 0fh, which are unimplemented. Is there any reason why these functions should not be implemented? The win31 sdk doesn't mention any restrictions on which INT21 functions can be used, neither does Schulman. Dave Pickles

2 1

Qusetion From New Developer
by Uhmmmm 11 May '01

11 May '01

I've been using WINE for a while now, and I thought it was just about time to start helping out. I found some very easy things I can fix (a lot of the FIXMEs in the basic controls (botton, static, etc)). The only problem is that, I'm not sure how to submit the code once I've fixed it. If someone could let me know, I could start coding. Thanks in advance.

3 2

__compar_fn_t Linuxism in dlls/wineps/afm.c
by Gerald Pfeifer 11 May '01

11 May '01

I believe relying on __compar_fn_t in dlls/wineps/afm.c is a Linuxism recently added to dlls/wineps/afm.c (and only there), Ian. Given that __compar_fn_t is only used in that single file and nowhere else, I'd suggest to simply use a typedef of your own instead of the non-portable __compar_fn_t. -- Could you please have a look? Alexandre, in the mean-time please consider my patch below, which gets rid of the build failure at least. /usr/bin/gcc -c -I. -I. -I../../include -I../../include -g -O2 -Wall -mpreferred-stack-boundary=2 -fPIC -D__WINE__ -D_REENTRANT -I/usr/X11R6/include -o afm.o afm.c afm.c: In function `SortFontMetrics': afm.c:686: `__compar_fn_t' undeclared (first use in this function) afm.c:686: (Each undeclared identifier is reported only once afm.c:686: for each function it appears in.) afm.c:686: syntax error before `UnicodeGlyphByNameIndex' afm.c:698: syntax error before `UnicodeGlyphByNameIndex' afm.c:718: syntax error before `UnicodeGlyphByUV' afm.c:729: syntax error before `AFMMetricsByUV' afm.c:691: warning: `pug' might be used uninitialized in this function afm.c: At top level: afm.c:644: warning: `UnicodeGlyphByNameIndex' defined but not used afm.c:649: warning: `UnicodeGlyphByUV' defined but not used afm.c:654: warning: `AFMMetricsByUV' defined but not used gmake[2]: *** [afm.o] Error 1 gmake[2]: Leaving directory `/.amd_mnt/vexpert/files8/test/wine/dlls/wineps' gmake[1]: *** [wineps/libwineps.so] Error 2 Thanks, Gerald Index: afm.c =================================================================== RCS file: /home/wine/wine/dlls/wineps/afm.c,v retrieving revision 1.13 diff -u -3 -p -r1.13 afm.c --- afm.c 2001/05/09 17:11:59 1.13 +++ afm.c 2001/05/11 10:58:58 @@ -683,7 +683,7 @@ static BOOL SortFontMetrics() qsort(aglCopy, PSDRV_AdobeGlyphList.size, sizeof(UNICODEGLYPH), - (__compar_fn_t)UnicodeGlyphByNameIndex); + UnicodeGlyphByNameIndex); } for (i = 0; i < afm->NumofMetrics; ++i) @@ -695,7 +695,7 @@ static BOOL SortFontMetrics() pug = bsearch(&ug, aglCopy, PSDRV_AdobeGlyphList.size, sizeof(UNICODEGLYPH), - (__compar_fn_t)UnicodeGlyphByNameIndex); + UnicodeGlyphByNameIndex); if (pug == NULL) { WARN("Glyph '%s' in font '%s' does not have a UV\n", @@ -715,7 +715,7 @@ static BOOL SortFontMetrics() /* typecast avoids compiler warning */ qsort((void *)(afm->Encoding->glyphs), afm->Encoding->size, - sizeof(UNICODEGLYPH), (__compar_fn_t)UnicodeGlyphByUV); + sizeof(UNICODEGLYPH), UnicodeGlyphByUV); for (i = 0; i < afm->Encoding->size; ++i) if (afm->Encoding->glyphs[i].UV >= 0) @@ -726,7 +726,7 @@ static BOOL SortFontMetrics() } qsort(afm->Metrics, afm->NumofMetrics, sizeof(AFMMETRICS), - (__compar_fn_t)AFMMetricsByUV); + AFMMetricsByUV); for (i = 0; i < afm->NumofMetrics; ++i) if (afm->Metrics[i].UV >= 0)

3 2

Wine Logo ?
by Marcus Meissner 11 May '01

11 May '01

Hi, Is the WINE Logo as used by WineHQ available somewhere in higher resolution? I need it for preparation of LinuxTag 2001 :) Ciao, Marcus

1 0

win32 binary DLLs -> Unix wrappers?
by Peter Duthie 11 May '01

11 May '01

What I would like to do is take an existing windows DLL for which I have the SDK but not the source, and write/generate a C++ wrapper that accesses the code contained therein, and be linked with existing unix programs. Eg, say I have X.DLL, X.LIB and X.h Is there a way using wine that I can generate wrapper code (say X_wrapper.cc), so that I can link it with a unix program that I would write around the wrapper? Thus I would have the benefits of developing under the unix environment and libraries, while utilising a necessary proprietary windows DLL. Note, native windows applications that use this DLL work fine when run under wine regularly. I cannot find documentation for this in the mailing list archives, or the official docs, although Chapter 5 of the winelib users guide seems to be the right place to look, it appears to not be written yet. Can anyone please direct me to relevant documentation/examples/code? Thanks, -peter

3 2

Re: Add support for NOMINMAX
by Alexandre Julliard 11 May '01

11 May '01

Francois Gouget <fgouget(a)free.fr> writes: > Why? It doesn't make a big difference but after all, if min/max are > defined in their own header, why not take advantage of it to avoid > duplication? (I hate duplicating code :-) Because that's not how Windows does it. And I think it's a good thing to avoid unnecessary dependencies between the Windows headers and the MSVC ones. -- Alexandre Julliard julliard(a)winehq.com

1 0

Re: Add support for NOMINMAX
by Francois Gouget 11 May '01

11 May '01

I noticed that you didn't apply this part of the minmax patch: --- cut here --- Index: include/windef.h =================================================================== RCS file: /home/cvs/wine/wine/include/windef.h,v retrieving revision 1.57 diff -u -r1.57 windef.h --- include/windef.h 2001/05/07 20:14:00 1.57 +++ include/windef.h 2001/05/11 01:17:37 @@ -14,6 +14,9 @@ #define WINVER 0x0500 #include "winnt.h" +#ifndef NOMINMAX +#include "minmax.h" +#endif #ifdef __cplusplus @@ -140,15 +143,6 @@ #define ADD_LOWORD(dw,val) ((dw) = ((dw) & 0xffff0000) | LOWORD((DWORD)(dw)+(val))) #endif -/* min and max macros */ -#ifndef NOMINMAX -#ifndef max -#define max(a,b) (((a) > (b)) ? (a) : (b)) -#endif -#ifndef min -#define min(a,b) (((a) < (b)) ? (a) : (b)) -#endif -#endif /* NOMINMAX */ #ifndef _MAX_PATH /* FIXME: These are supposed to be in stdlib.h only */ --- cut here --- Why? It doesn't make a big difference but after all, if min/max are defined in their own header, why not take advantage of it to avoid duplication? (I hate duplicating code :-) -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ La terre est une bêta...

1 0

Jump to page:

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