- Wine-Devel - list.winehq.org

Scrollbars and scrollwheel: -fomit-frame-pointer problems
by Diego 'Flameeyes' Pettenò Sept. 18, 2004

Sept. 18, 2004

Hi, Seems like I found out which flags causes trouble with the scrollbars and the mouse's scrollwheel: building wine without -fomit-frame-pointer flag makes it work right. This fixes my problem ( http://article.gmane.org/gmane.comp.emulators.wine.devel/23780 ) and seems to fix (at least for me) the problem reported by Nguyen Tuan Anh ( http://article.gmane.org/gmane.comp.emulators.wine.user/7169 ). I actually don't know how to filter with autoconf and stuff the specified flag, I only know with gentoo's portage, but I hope there's a way to make this flag doesn't go to the gcc parameters. Regards, -- Diego "Flameeyes" Pettenò dgp85(a)users.sourceforge.net - http://flameeyes.web.ctonet.it/

6 10

Re: Added service database names
by Dmitry Timoshkov Sept. 18, 2004

Sept. 18, 2004

"Alexander Yaworsky" <yaworsky(a)migusoft.ru> wrote: > +#ifdef UNICODE > +# define SERVICES_ACTIVE_DATABASE SERVICES_ACTIVE_DATABASEW > +#else > +# define SERVICES_ACTIVE_DATABASE SERVICES_ACTIVE_DATABASEA > +#endif Wine uses WINELIB_NAME_AW macro in order to simplify '#ifdef UNICODE' magic, so in the above case it would look like this: #define SERVICES_ACTIVE_DATABASE WINELIB_NAME_AW(SERVICES_ACTIVE_DATABASE) -- Dmitry.

2 1

Terminal Font
by pcunite＠fsmail.net Sept. 18, 2004

Sept. 18, 2004

I have a windows app that works really well under wine. I have placed the fonts from my XP workstation to my Fedora 2 wine directory in "./wine/windows/fonts/" so that I could have more fonts available to the app. My problem is that the "Terminal" font is not showing up when using a windows API "Font Dialog". Where can I get this "Terminal dos/oem" font? Thank you Jason -- Whatever you Wanadoo: http://www.wanadoo.co.uk/time/ This email has been checked for most known viruses - find out more at: http://www.wanadoo.co.uk/help/id/7098.htm

2 1

Help with GetConsoleWindow()
by Ewert, Mark Sept. 18, 2004

Sept. 18, 2004

I'm running an application that calls the stubbed out function GetConsoleWindow(). I want the application to stay in the dos console when it runs but unfortunately when it sees a NULL from GetConsoleWindow() it loads a graphical window. I tried hacking the function to return the value 1 and this gave me the result I had hoped where it did not call up a graphical window but at a later point I get the error: wine: Unhandled exception (thread 000d), starting debugger... Any ideas on what GetConsoleWindow() should actually return? Cheers, Mark

3 2

Wine-20040918 preblems in
by Green, Shaun E. Sept. 18, 2004

Sept. 18, 2004

Wine does not function correctly under Yoper Linux with kernel 2.6.8.1-7 (this kernel has performance patches applied). It seems to build fine, but it does not run correctly and running MFC apps do not even open. I tried changing the /tmp link in dosdevices directory, etc but to no avail. I've tried previous Wine versions and stable May release, but same results. Codeweavers crossover office works, but it's too slow for my purposes. I've used Wine-20040818 successfully since it's release on Yoper Linux with kernel 2.4.26 vanilla, so that's why I'm betting it's a kernel 2.6.8.1 issue. Can anyone help? Shaun

2 1

Re: dinput header fixes
by Alexandre Julliard Sept. 18, 2004

Sept. 18, 2004

Robert Reif <reif(a)earthlink.net> writes: > Add some more version checks. As a rule we avoid such version checks in Wine, they are not necessary and will only cause trouble since we compile our code with the same headers. I know there are some similar checks in there already but they should probably be removed. -- Alexandre Julliard julliard(a)winehq.org

2 2

Re: buffer: ref count cleanup
by Robert Reif Sept. 18, 2004

Sept. 18, 2004

James Hawkins wrote: >Changelog > * Use InterlockedDecrement and InterlockedIncrement instead of ++/--. > > > That ref doesn't belong to a com object. I belongs to a duplicated memory buffer and should probably be protected by a lock someday.

1 0

[OT] AMD64 Implications
by Ann and Jason Edmeades Sept. 17, 2004

Sept. 17, 2004

Hello, Slightly off topic, but I am looking at purchasing a new PC and intend to continue doing wine development on it (especially d3d9). Is there any wine implications to buying an AMD64 compared to a 'normal' 32 bit chip. Will I be able to continue my wine development, obviously for running emulation of 32 bit windows apps (games)? Would I need to ensure I use 32 bit kernels, or can I make use of any 64 bit ones (dont know if these exist even!). Sorry if this is an obvious question, but I didnt want to go so far and find I have caused myself problems Jason

2 1

Re: fonts: wine_marlett
by Ivan Leo Puoti Sept. 17, 2004

Sept. 17, 2004

> That works but then we're maintaining two codepaths, one or other of > which will hardly be tested at all. Why not just check in the font > binaries? What is required to build the fonts? Should I install fontforge? I've been in hospital with appendicitis and haven't followed wine development recently. Ivan.

1 0

Re: olefont: ref count cleanup
by Robert Shearman Sept. 17, 2004

Sept. 17, 2004

James Hawkins wrote: >Changelog > * Use InterlockedDecrement and InterlockedIncrement instead of ++/--. > > Again, all of these patches do not fix the whole point about using the Interlocked* functions, which is that the variable must always be used *atomically*. That means if you grep the file for uses of "This->ref" (or the equivalent) then they should all only be as parameters to Interlocked* functions. Rob

2 2