April 2004 - Wine-Devel - list.winehq.org

Re: bug in winemine about box

by Blake Leverett

this seems to be broken on win2k3, even if run in compatibility mode. See attached screenshot. It's OK on wine, and I don't have other versions of windows to test. Ivan. Are you really running a windows version of winemine under XP running in Bochs? Or is the screen shot misleading? Blake

April 1, 2004

Re: Fwd: Re: Source code visualization tools?

by Joshua Walker

You are looking for "Source Navigator" It's here... http://sourcenav.sourceforge.net/ It's pretty cool if you want to follow what goes where. All the pretty arrows too. (It's horazontal along the top of the screen, not vertical) You can follow functions, stucts, header files. I used it when I was a programmer... :) -halkun --- Blake Leverett <bleverett(a)att.net> wrote: > > Joel Konkle-Parker wrote: > > > Is there such a thing as a source code > visualization tool that makes a > > "map" of a program's source? Kind of like: > > > > main() > > | > > | > > function1() > > /\ > > / \ > > func2() func3() > > | > > | > > func4() > > > > I'm basically looking for something that will > help me "see" how a > > program is laid out so that I can start working > on it. > > > > Thanks in advance. > > > > > > I was looking for a similar thing a while back. > One great tool for > navigating the wine source is the etags program. > In the wine source > directory, type 'make etags'. This makes a file > called TAGS. Then, start > emacs, and type alt-x visit-tags-table, and load > the tags file. You can > navigate the source by function. See the tags > manpage and the emacs > manpage for the tags section for details. > > Blake > > > `--------------- Forwarded message (end) > >

April 1, 2004

Re: bug in winemine about box

by Francois Gouget

On Tue, 30 Mar 2004, Ivan Leo Murray-Smith wrote: > this seems to be broken on win2k3, even if run in compatibility mode. See > attached screenshot. It's OK on wine, and I don't have other versions of windows > to test. It looks like it's just an issue with the font size that's a bit bigger than expected so that the text does not fit in the space that's defined in the RC file... -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ Good judgment comes from experience, and experience comes from bad judgment -- Barry LePatner

April 1, 2004

Re: [patch] Wine 20040309: documentation patche

by Vincent Béron

Le mer 31/03/2004 à 11:49, Peter Hanecak a écrit : > Hello, > > while building Wine on "RedHat 9"-like system I encountered two typo in > Wine documentation which prevented me from "compiling" documentation with > docbook2html (docbook-utils-0.6.12-5). The fix is correct, but it's already been applied to cvs on March 11. Usually, it's best to confirm that the bug still exists in current cvs before writing/sending a fix, else there's a real probablitity to duplicate some work. And that probability goes up as time goes by. Vincent

April 1, 2004

Re: Winelib Test Drive problem

by Francois Gouget

On Thu, 31 Mar 2004, greensh(a)knology.net wrote: > Hi, > > I'm starting to use the latest winelib (wine-20040309 release) to try > eventually compiling an windows MFC app I wrote. Before attempting this > however, I'm following all directions in the winelib user guide, but the > Test Drive fails and so it tells me to post to this mailing list. The problem is that the Winelib User Guide is very out of date. winemaker has been changed recently and no longer integrates with autoconf. Also it uses winegcc and winebuild instead of calling gcc directly. Finally it does not support dlls though now that the required support has been added to winegcc it should be possible. [...] > winebuild -o winemine2.exe.dbg.c --debug -C. dialog.c main.c > winegcc -c -mno-cygwin -I. -o winemine2.exe.dbg.o winemine2.exe.dbg.c > winegcc -c -mno-cygwin -I. -o dialog.o dialog.c > winegcc -c -mno-cygwin -I. -o main.o main.c > wrc -I. -foEn.res En.rc > En.rc:23:22: Error: syntax error However this error has nothing to do with the above issues. winemaker automatically creates Makefiles by analyzing the source code. However this is an impossible task to get right in 100% of the cases (even for a human can be hard to do right). So some heuristics are used that work most of the time. Unfortunately the person who wrote the 'Test Drive' chose a case where the heuristics fail and did not mention it. The error is caused by the presence of multiple rc files (maybe there was only one rc file at the time the Test Driver was written). Only one RC file is supposed to be compiled but winemaker does not know that and wouldn't know which one is supposed to be compiled anyway. So it tries to compile them all and this is what causes the error. Just edit the generated Makefile and edit the list of RC files so only rsrc.rc is listed and it should work better. -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ If it stinks, it's chemistry. If it moves, it's biology. If it does not work, It's computer science.

April 1, 2004

Re: winapi_stats

by Francois Gouget

On Wed, 31 Mar 2004, Tom wrote: > Hi, > > http://www.winehq.org/site/winapi_stats > > Is incorrect as it shows Total 19640 100% > 100% would be nice but its incorect! I just noticed that there are some extra dlls to filter out: ttydrv winealsa.drv winearts.drv wineaudioio.drv wined3d winedos winejack.drv winemp3.acm winenas.drv wineoss.drv wineps wineps16.drv I guess the .dll extension is implicit. It would be nicer with it but that's just my personal preference. Also, x11drv was supposed to be filtered out already and yet it is listed, and with 4 stub at that! But if I check today's x11drv.spec file there are no stubs in x11drv so something is very wrong... Similarly winearts.drv is shown as having 2 stubs out of supposedly 5 APIs and yet it's spec file in its entirety is: @ stdcall DriverProc(long long long long long) ARTS_DriverProc @ stdcall wodMessage(long long long long long) ARTS_wodMessage @ stdcall widMessage(long long long long long) ARTS_widMessage Only 3 APIs and no stub here! Also apparently the 16bit dlls are listed before the 32bit dlls. But the separation is not clear so it's confusing. Personally I'd prefer a plain alphabetical list that mixes 16 and 32 bit dlls. Maybe add '(16bit)' to those dlls that are 16 bit. -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ Indifference will certainly be the downfall of mankind, but who cares?

April 1, 2004