wine-devel July 2003

wine-devel@winehq.org

111 participants
281 discussions

Re: Trackbar size fixes
by Duane Clark 01 Aug '03

01 Aug '03

Mike Hearn wrote: > On Tue, 2003-07-29 at 05:19, Duane Clark wrote: > >>I have done quite a bit of comparison testing with ControlSpy on Wine >>and Win2K, so these changes should be accurate. Mainly done to fix >>earthquake (which was completely broken). >> >>Changelog: >> Fix the size/position of the thumb/channel/tics to match Win. > > > There's clearly something strange going on here we don't fully > understand - this patch breaks Internet Explorer again. See attached > screenshot. Builtin after this patch is on the left, native (98) is in > the middle, CVS wine is on the right. Hmm, attached is what that looks like for me. So I don't know why it looks bad to you. > Horizontal trackbars are still OK, though with this patch the thumb is > bigger than native 98. I didn't bother with a screenshot of that since > it still looks OK. One part of the code I did not test is the function TRACKBAR_InitializeThumb(), which sets the initial thumb length. My confidence in that part is not very good, since it doesn't make sense to have different calculations for the horizontal and vertical bars. So if someone were to do some simple testing to verify/correct that function, it would be a good thing. All of the rest of the patch sets the rest of the dimensions of the control based on the length of the thumb and the size of the window, which is how Windows does it. That part I tested extensively, and am very confident is correct.

4 8

Website Question
by dd jj 31 Jul '03

31 Jul '03

Hello Everyone, Does anyone know a website listing all the Win32 API calls and their X window API equivalents or Unix command equivalents? Thank you --------------------------------- Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software

1 0

Licensing Question
by Anthony Tuininga 31 Jul '03

31 Jul '03

The MingW32 project is developing its own set of Windows headers under a different license than Wine (which uses LGPL, right?) and I have noticed (using both projects) that the Wine headers are more complete in a number of areas. I was wondering if it would be acceptable to use the Wine headers as a source for filling in gaps in the MinGW32 headers? In essence, would the Wine group be willing to allow this cross pollination since (clearly) it would be a violation of the licenses as they stand today. Any thoughts on this? Or am I treading into a minefield?? :-) -- Anthony Tuininga anthony(a)computronix.com Computronix Distinctive Software. Real People. Suite 200, 10216 - 124 Street NW Edmonton, AB, Canada T5N 4A3 Phone: (780) 454-3700 Fax: (780) 454-3838 http://www.computronix.com

5 4

Expect deadlock!
by Marcelo Duarte 31 Jul '03

31 Jul '03

Hi all, Somebody could help saying me what it means the messages below and where I must look for to finish with them? Thank you! err:win32:_EnterSysLevel (0x4087eda8, level 2): Holding 0x4092f8e0, level 3. Expect deadlock! err:win32:_EnterSysLevel (0x4087eda8, level 2): Holding 0x4092f8e0, level 3. Expect deadlock! err:win32:_EnterSysLevel (0x4087eda8, level 2): Holding 0x4092f8e0, level 3. Expect deadlock! err:win32:_EnterSysLevel (0x4087eda8, level 2): Holding 0x4092f8e0, level 3. Expect deadlock! err:win32:_EnterSysLevel (0x4087eda8, level 2): Holding 0x4092f8e0, level 3. Expect deadlock! err:win32:_EnterSysLevel (0x4087eda8, level 2): Holding 0x4092f8e0, level 3. Expect deadlock! err:win32:_EnterSysLevel (0x4087eda8, level 2): Holding 0x4092f8e0, level 3. Expect deadlock! err:win32:_EnterSysLevel (0x4087eda8, level 2): Holding 0x4092f8e0, level 3. Expect deadlock! err:win32:_EnterSysLevel (0x4087eda8, level 2): Holding 0x4092f8e0, level 3. Expect deadlock! err:win32:_EnterSysLevel (0x4087eda8, level 2): Holding 0x4092f8e0, level 3. Expect deadlock! -- Marcelo Duarte

4 4

Unhandled exception (wine-20030709)
by Magnus Solvang 30 Jul '03

30 Jul '03

(I posted this to the wine-users-list a week ago, but didn't get any respons) I just tried to install wine for my first time. Redhat 9.0, kernel 2.5.73. Downloaded the rpm-binary, but when trying to start notepad.exe, it looped with a message like: wine: Unhandled exception (thread 01f9), starting debugger... Could not stat /mnt/fd0 (No such file or directory), ignoring drive A: While looping it started nearly 255 processes (max PTYs?), before the machine halted. I did this before modifying my config-file (using the default one). After adjusting the config-file, I no longer got any error-messages, but the same thing happened. [...] wine: Unhandled exception (thread 01f1), starting debugger... wine: Unhandled exception (thread 01f3), starting debugger... wine: Unhandled exception (thread 01f5), starting debugger... wine: Unhandled exception (thread 01f7), starting debugger... wine: Unhandled exception (thread 01f9), starting debugger... wine: Unhandled exception (thread 01fb), starting debugger... Fine! I then tried to compile wine from source, but at the end of the installation (su root/make install - wine only), the same thing happened: [...] wine: Unhandled exception (thread 01f5), starting debugger... Could not stat /mnt/fd0 (No such file or directory), ignoring drive A: Could not stat /cdrom (No such file or directory), ignoring drive D: wine: Unhandled exception (thread 01f7), starting debugger... Could not stat /mnt/fd0 (No such file or directory), ignoring drive A: Could not stat /cdrom (No such file or directory), ignoring drive D: wine: Unhandled exception (thread 01f9), starting debugger... Could not stat /mnt/fd0 (No such file or directory), ignoring drive A: Could not stat /cdrom (No such file or directory), ignoring drive D: wine: Unhandled exception (thread 01fb), starting debugger... Could not stat /mnt/fd0 (No such file or directory), ignoring drive A: Could not stat /cdrom (No such file or directory), ignoring drive D: wine: Unhandled exception (thread 01fd), starting debugger... ./tools/wineinstall: line 645: 26966 Killed $REGEDIT $DEFREG >/dev/null Registry install failed. I managed to open a terminal and do a "killall -9 wine". This happened during "make install", so I didn't get to edit the config-file before this happened. I have tried booting with both 2.4 and 2.5-kernels, with the same result. - M

2 2

fontview.exe...
by Jonathan Wilson 30 Jul '03

30 Jul '03

Its used by windows to display fonts before and after installation. And I know of at least one setup program (might have been a Corel app, I forget) that displays a long list of fonts which you can select from to install and then uses fontview.exe (I think its fontview.exe, it loks very similar anyhow) for previewing the fonts (so you can see what they look like before they are installed). Anyone want to comment on this: 1.does anyone else remeber the app and/or the dialog? 2.does anyone know if it really is fontview.exe? 3.does wine need a fontview.exe? and 4.if I was to code a fontview.exe, would it be of use to anyone (wine, reactos etc)?

2 1

Strange behavior on build
by David D. Hagood 29 Jul '03

29 Jul '03

I'm having a strange behavior trying to build Wine on my machine at work (which is a modified RH7.3 machine): First of all, if I attempt to do a standard CVS checkout followed by a make depend, the make depend failes with a "dlls - no such directory" error, even though it exists. Changing SHELL=/bin/sh to SHELL=/bin/bash in Make.rules and re-running configure fixes this, but then I get stuck in a loop building - it looks like the makefile starts building the dependancy "wine", then builds "libs", then decides it needs to build "wine" to build "libs" and starts that, then builds "libs".... I'm at a bit of a loss to explain the behavior, so does anybody have any good suggestions? Versions: GNU bash, version 2.05b.0(1)-release (i586-redhat-linux-gnu) Copyright (C) 2002 Free Software Foundation, Inc. GNU Make version 3.79.1, by Richard Stallman and Roland McGrath. Built for i386-redhat-linux-gnu Linux version 2.4.20-openmosix1 (root@(none)) (gcc version 2.96 20000731 (Red Hat Linux 7.3 2.96-113)) #1 Sun Jan 12 04:18:51 CST 2003 (if you would be so kind, please copy my work address of David decimalpoint Hagood ('A'-1) aeroflex decimalpoint com since I am only subscribed to the list on my personal email).

1 0

API tracking and documentation
by Steven Edwards 29 Jul '03

29 Jul '03

Hello, The ReactOS project is interested in making a change to WINE the function commented that would make API tracking a little nicer. We have implemented a web page like the mono project has that shows the implemented and unimplemented functions in the API. Will the WINE project accept patches to the comments to support this type of tracking system? It would be nice because you guys could implement the same thing on your website. If the answer is no it is REALLY going to be a PITA for us to diff our sources to yours for every function. Please take a momenet to look at the site and how it works. http://reactos.wox.org/index.php?page=apistatus Here is the documentation for how we do it. Abstract Explains what tags are and how to use them. TABLE OF CONTENTS * 1 Overview * 2 MS API compatibility 1 Overview We define tagging a function as the process of associating metadata with a function. We define a tag to be a piece of information that has a well-defined meaning. A tag has one attribute - a name. The name of a tag always begin with the at sign (@) and it can include only the letters a-z and digits 0-9 and the underscore (_). Tagnames are case-insensitive. In the future a tag could have one more attribute - a value, but this is currently not needed. In ReactOS, tags are currently only used to track compatibility with Microsoft APIs, but it could be used for so much more. Tags are applied to functions by including them in a comment just before the function. Eg. if you have a function called MyFunction, then you can tag it with the tag @mytag like this: /* * @mytag */ VOID MyFunction() { } 2 Microsoft API compatibility Two tags are defined to track compatibility with Microsoft APIs. @implemented and @unimplemented. Apply @implemented to functions which match and behaves like a Microsoft API. Use @unimplemented to functions which match, but does not behave like a Microsoft API. The regenstat tool (located in reactos/tools/rgenstat) will parse the source code for these tags and generate an xml file containing functions that have these tags. The xml file can be processed by the rapistatus.xsl xml stylesheet (located in reactos/tools/rgenstat/web) to create an html file suitable for display using a browser. __________________________________ Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! http://sbc.yahoo.com

3 3

Re: Trackbar size fixes
by Mike Hearn 29 Jul '03

29 Jul '03

Odd, I remember doing some work on the trackbar a few months ago (it was pretty broken). Testing against the native comctl32 from Windows 98 showed that I got it pretty close - do you have before/after screenshots for this patch? Perhaps the trackbar looks different in 98 vs 2K. -- Mike Hearn <m.hearn(a)signal.qinetiq.com> QinetiQ - Malvern Technology Center

3 2

WineHQ website (lostwages) url changes
by Jeremy Newman 29 Jul '03

29 Jul '03

I spent some time today working on the lostwages codebase. I finally discovered how to get PHP to see the PATH_INFO without getting a 404. Seems you need to put "AllowPathInfo On" in the .htaccess. In doing so, I can get rid of the ugly ?page=about urls and instead use /site/about. I updated .htaccess to catch the old urls and put them to the new style. NOTE to template authors, if you want to put a relative link in the site from now on, use {$root} to have the site put the correct path in for you. For example, <a href="{$root}/site/about">About Wine</a>. This also works for images: <img src="{$root}/images/foo.jpg"> -- Jeremy Newman <jnewman(a)codeweavers.com> CodeWeavers, Inc.

2 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 July 2003