wine-devel May 2005

wine-devel@winehq.org

145 participants
348 discussions

Re: PATCH: add test for non existing directory during createfile
by Stefan Leichter 05 May '05

05 May '05

Am Donnerstag, 5. Mai 2005 18:59 schrieb Marcus Meissner: > Hi, > > I would like to have someone test this test on windows... > > I have the suspicion that Windows might create non-existing directories > in the middle. > > Ciao, Marcus > Hello Markus, the test succeeds on my NT4 box Bye Stefan

2 1

InstallShield status page on the wiki
by Mike Hearn 05 May '05

05 May '05

Hi, I created an InstallShield page on the new wiki: http://wiki.winehq.com/InstallShield Dimi, the <p> tags don't seem to create any bottom padding like they would normally so all the text seems squashed together even if they have newlines between them. Can this stylesheet problem be fixed? thanks -mike

3 5

Re: [patch] fix delete key on certain european keyboards
by Paul van Schayck 05 May '05

05 May '05

On 5/5/05, zhilla <zhilla(a)spymac.com> wrote: > sorry if double, resend... > well, this is just this: > http://bugs.winehq.org/show_bug.cgi?id=2400 > and should apply to today's cvs. > i AM NOT the author! I have no idea how correct this patch is but I see a few things wrong with the patch style. It's missing a Changelog entry. It uses c++/c99 comment style (//). And the patch is made from the dlls/x11drv/ dir and not the cvs root. Paul > --- keyboard.c.orig 2005-05-05 18:22:56.000000000 +0200 > +++ keyboard.c 2005-05-05 17:41:03.000000000 +0200 > @@ -1067,11 +1067,14 @@ > else > XLookupString(e, NULL, 0, &keysym, NULL); > > - if ((keysym >= 0xFFAE) && (keysym <= 0xFFB9) && (keysym != 0xFFAF) > - && (e->state & NumLockMask)) > - /* Only the Keypad keys 0-9 and . send different keysyms > - * depending on the NumLock state */ > - return nonchar_key_vkey[keysym & 0xFF]; > + if (e->state & NumLockMask) // NumLock is active > + {if (keysym == 0xFFAC) // Numeric Del pressed > + return keyc2vkey[0x3B]; // comma > + if ((keysym >= 0xFFAE) && (keysym <= 0xFFB9) && (keysym != 0xFFAF)) > + /* Only the Keypad keys 0-9 and . send different keysyms > + * depending on the NumLock state */ > + return nonchar_key_vkey[keysym & 0xFF]; > + } > > TRACE_(key)("e->keycode = %x\n", e->keycode); > > >

1 0

Re: Cannot compile man pages outside source directory
by Alexandre Julliard 05 May '05

05 May '05

William Poetra Yoga H <williampoetra(a)yahoo.com> writes: > Why shouldn't we have absolute paths in makefiles? It makes it impossible to copy or move build trees around, that's very annoying. -- Alexandre Julliard julliard(a)winehq.org

1 0

Missing HAVE_V4L2 check
by Francois Gouget 05 May '05

05 May '05

Maarten, could you fix the following winapi_check warnings: dlls/avicap32/avicap32_main.c: HAVE_V4L2 is not declared as a conditional dlls/avicap32/avicap32_main.c: HAVE_V4L2 is not declared as a conditional The problem is that dlls/avicap32/avicap32_main.c checks for HAVE_V4L2 but we lack the appropriate check in configure.ac and the macro declaration in include/config.h. -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ Dieu dit: "M-x Lumi\xE8re". Et la lumi\xE8re fut.

1 0

Re: Cannot compile man pages outside source directory
by William Poetra Yoga H 05 May '05

05 May '05

--- Alexandre Julliard <julliard(a)winehq.org> wrote: > > No, you don't want to put absolute paths in makefiles. c2man should be > fixed to load files from the source directory if they are not found in > the build directory. > Why shouldn't we have absolute paths in makefiles? OK, I'll take a look at c2man.pl and see what I can do (though I've never spoken Perl before). Or maybe someone more fluent in Perl can fix this? What I have in mind is add an option -S that gives the source directory (shouldn't be too difficult, right?) William Poetra Yoga Hadisoeseno __________________________________ Do you Yahoo!? Make Yahoo! your home page http://www.yahoo.com/r/hs

1 0

Re: winecfg: Add wine configuration tab
by Dimitrie O. Paun 05 May '05

05 May '05

On Thu, May 05, 2005 at 12:50:50AM -0500, James Hawkins wrote: > I used the options specified for [wine] in the Wine Options Status > page [1] to create a new wine options tab for winecfg. I think we intentionally omitted such a page before. The thinking is that these are really low-level settings that normal users shouldn't touch. Those who *need* to for whatever strange reason can use regedit to do so. This is why it is important to have an up-to-date status_options page to begin with, so that people at least have a chance of knowing what options are available (for those not accessible via winecfg). -- Dimi.

3 2

Re: winecfg: Add wine configuration tab
by Dimitrie O. Paun 05 May '05

05 May '05

On Thu, May 05, 2005 at 12:50:50AM -0500, James Hawkins wrote: > [1] http://winehq.org/site/status_options I'm afraid this page is a bit out of date. It needs lots of love, and I think it would be a worthwhile project to update it. -- Dimi.

1 0

Better PolyLine drawing
by Rein Klazes 05 May '05

05 May '05

Hi, cc to wine-devel: I may overlooked something here. The patch fixes a problem in BigJig a jigsaw puzzle game (free download at www.lenagames.com) when it generates the pieces. The jigsaw piece shapes are generated with a series of short (5-7 points) Polyline calls, followed by a call to FloodFill. Unfortunately in Wine there are sometimes gaps between the polyline segments, leaking the floodfill. In Windows if a line or polyline is drawn from x1,y1 to xn,yn , the pixel at x1,y1 is always painted and the one at xn,yn not (unless it is also painted as another part of the segment), that guarantees that there are no gaps. X11DRV_PolyLine refuses to use the pen if the pen width is zero, it changes the width to 1 instead. This causes 'X' to use an alternate line drawing algorithm, more focused on pleasing appearance then on details like mentioned above. Setting the pen width to zero make all the problems go away. I do not know why the pen width is set to zero, this came into wine somewhere in 1998 before the change to cvs. Arguments against it are: - line drawing with pen width 1 are not like in Windows, in contrast to width 0 are very much like in Windows; - line drawing with pen width 1 is slower; - PolyPolyLine, LineTo and all other algorithms in wine do not do this; - Xlib programming manual recommends not to mix pen with 0 and pen width 1 drawing. I have looked at this both on a Debian XFree86 system and a Suse 9.2 with XOrg. Changelog: dlls/x11drv : graphics.c, pen.c Don't set the pen width to 1 in X11DRV_PolyLine. Rein.

1 0

GetExitCodeProcess always returns 1
by Igor Sysoev 05 May '05

05 May '05

2 years ago I reported that on FreeBSD Wine-20030508's GetExitCodeProcess() always returns 1: http://www.winehq.org/hypermail/wine-devel/2003/06/0100.html It was fixed by patch: http://www.winehq.org/hypermail/wine-devel/2003/06/0381.html and I used the patched Wine-20030508 all the time to run MSVC, OpenWatcom C, and Borland C in a command line. However, when I try to run dmc.exe, sc.exe, or make.exe from Digital Mars C/C++ Compiler, I always see the message: wine: Unhandled exception (thread 0009), starting debugger... I build Wine-20050310, but it has the same two problems: 1) GetExitCodeProcess() always returns 1 on FreeBSD 5.3, 2) and wine could not run Digital Mars C/C++ Compiler. Digital Mars C/C++ Compiler is could be downloaded here: http://www.digitalmars.com/download/freecompiler.html Igor Sysoev http://sysoev.ru/en/

2 1

← Newer
1
...
28
29
30
31
32
33
34
35
Older →

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 May 2005