wine-devel

wine-devel@winehq.org

2 participants
84469 discussions

Re: Small fixes in controls/menu.c
by gerard patel 22 May '01

22 May '01

At 10:20 AM 20/05/2001 -0700, you wrote: >gerard patel <gerard.patel(a)asi.fr> writes: > >> (patch using NC_HandleNCCalcSize instead of SetWindowPos) >> >> IMO it's better and it solves my problem as well. > >I think the SetWindowPos one was better. If the app handles >WM_NCCALCSIZE we shouldn't try to bypass it. But does Windows send this message in this case ? From what I can see in the traces, I don't think so. Maybe Maciek could look at the behaviour of his app under Windows. Or I could download it and try to solve the problem myself (I'd better not :-/) Gerard

2 1

Re: Wine build failure in tools/winebuild/spec16 due to recent change
by Ove Kaaven 21 May '01

21 May '01

On Mon, 21 May 2001, Marcus Meissner wrote: > Changelog: > In case our stat already supports 64bit operations (like FreeBSD > stat does), we don't need to stub them, we can just define the > x64 functions to x. You know, glibc would also have such an interface if you used the -D_FILE_OFFSET_BITS=64 compilation option. Wouldn't it be simpler to unify the 64-bit interface code by using that?

1 0

Re: warning fixes
by Francois Gouget 21 May '01

21 May '01

On Mon, 21 May 2001, eric pouech wrote: > ChangeLog: fixed a couple of warnings This does not fix the warnings, it just hides the bug. As the comments say, the assignments are plain wrong in the first place. /* FIXME: This is plain wrong, we must convert from a '\0' separated * memory block to an array of pointers to string format. */ - MSVCRT__environ = GetEnvironmentStringsA(); + MSVCRT__environ = (char**)GetEnvironmentStringsA(); MSVCRT___initenv = MSVCRT__environ; /* FIXME: This is plain wrong, we must convert from a '\0' separated * memory block to an array of pointers to string format. */ - MSVCRT__wenviron = GetEnvironmentStringsW(); + MSVCRT__wenviron = (WCHAR**)GetEnvironmentStringsW(); MSVCRT___winitenv = MSVCRT__wenviron; -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ Avoid the Gates of Hell - use Linux.

1 0

Anybody know int-31?
by Bob Goodwin 21 May '01

21 May '01

I want to run an application that requires win95 but relys heavily on DOS interupt functions. Specifically it requires interupt 31 which is just a stub in Wine. It appears (from R.B.'s list) that there is no limit on calls to interupt_31-AX=0305 (request the address of (?:the:a) save/restore handler.) That implies more than one thread could have a save/restore pointer. When calling the save/restore handler function, the only parameter passed is a byte in AL to indicate whether to save the current context or restore a saved context. My question is, are there multiple copies of the save/restore function or at least multiple entry points? It seems that this would be the only way of having multiple unique context saves. It would be differrent if a unique `handle' was returned by int_31 instead of a call address. If only one context can be stored at a time, do I need a spin-lock within the save/restore function to keep other applications holding until their turn? Thanks. Bob Goodwin

1 0

Re: Networking with Mandrake 8.0 and SuSE 7.1
by Steve Fox 21 May '01

21 May '01

This weekend I upgraded to Mandrake's 2.4.4 kernel from Cooker (since it fixed both my mouse and token ring) and suddenly this problem has gone away (using Notes 5.0.7 and wine-20010305). I'm still planning to go through Mandrake's 2.2.19 SRPM and find which patch messes things up (I can't use a Linus-only kernel because I need reiserfs). I will post again once I have narrowed down the list of suspects. I'm guessing it has to be a common patch since SuSE seems to have the same symptoms. Steve Fox IBM Linux Technology Center http://www.ibm.com/linux/ltc http://k-lug.com

1 0

Re: Small fixes in controls/menu.c
by Alexandre Julliard 21 May '01

21 May '01

gerard patel <gerard.patel(a)asi.fr> writes: > But does Windows send this message in this case ? From what > I can see in the traces, I don't think so. Maybe Windows does this differently then. But doing the NC calculation without sending a WM_NCCALCSIZE does not seem right. -- Alexandre Julliard julliard(a)winehq.com

1 0

Re: More breakages
by Alexandre Julliard 21 May '01

21 May '01

gerard patel <gerard.patel(a)asi.fr> writes: > There is a nice FIXME in the new message handling around the > old timer handling code, so maybe fix is pending ? I guess you could say that... Hardware messages need to be integrated into the new queue handling, I'm working on it but it will probably take a few days. -- Alexandre Julliard julliard(a)winehq.com

1 0

Re: More breakages
by gerard patel 20 May '01

20 May '01

At 10:28 AM 20/05/2001 +0200, I wrote: >(one more time following up to myself) >Now searching for the Acrobat Reader funny scrolling... I guess that this one is probably because of a still incomplete implementation; what happens is : - I click in the vertical scrollbar - the text begins to scroll (for some reason this particular text is very slow to scroll) - the scroll timer expires and scrolls again the page The WM_LBUTTONUP (supposed to end this loop) is not received until 20 pages later. If I test with a text that scrolls much faster, the problem is much less severe (only one page too much). It seems to be a message order problem; before Wine had - hardware messages (mouse, keyboard) - timer Now it is - timer - hardware messages There is a nice FIXME in the new message handling around the old timer handling code, so maybe fix is pending ? Gerard

1 0

Re: More breakages
by gerard patel 20 May '01

20 May '01

At 02:49 PM 20/05/2001 +0200, you wrote: >That sounds correct, even for all mailing lists, not just wine-cvs. The >hypermail archives at winehq.com is updated simultaneously with the list >mail being sent out to all subscribers. Ah, I was not understanding how the moderation is working (just read Andi's explanations on cemw). So the extraordinary delays I see sometimes on my posts to wine mailing lists are probably caused by my ISP beta testing IP on avian carriers. >(This is not the case with the >integrita archives, though, since integrita is just one of the >subscribers, subject to the whims of the MTA.) Did you use Reload? It's hard to remember what I did past 2 in the morning. I think that the following morning I looked only at Integrita; they seem to have not taken in account anything since. I'll take a look more accurately next time. Thanks for the explanations. Gerard

1 0

What about XP?
by Uhmmmm 20 May '01

20 May '01

Just wondering: Is there anything being done to update wine for windoze XP?

2 1

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