wine-devel

wine-devel@winehq.org

8 participants
84486 discussions

Re: [Fwd: Re: Oh yeah, the docu...]
by Tony Lambregts 14 Mar '02

14 Mar '02

> On Wed, Feb 20, 2002 at 09:40:43AM -0700, Tony Lambregts wrote: >> Tony Lambregts wrote: [Snip] >>> Ok so its just the online doc thats not up to date. Thanks. >>> >>> http://www.winehq.com/Docs/wine-user/configuring.shtml >>> >>> also looks like the the following are also not up to date. >>> >>> http://www.winehq.com/Docs/winedoc-sgml.tgz >>> http://www.winehq.com/Docs/winedoc-pdf.tgz VERY OLD >>> http://www.winehq.com/Docs/winedoc-ps.tgz VERY OLD >>> >>> and I would suspect that these too. (did not actually download) >>> >>> http://www.winehq.com/Docs/wine-set-html.tgz >>> http://www.winehq.com/Docs/winedoc-html.tgz >> [snip] >>> Since my last post on usenet I did download these and they are >>> out of >> date too. IMHO www.winehq.com/Docs should be updated at each >> snapshot. > Yeah, like I was really dying for finally seeing this being done. > > This time I yelled yet again, and Jeremy White muttered some Holy > Promise to make it finally work. (which, on hindsight, is a > relatively cheap promise due to Codeweavers having to go through > the trouble of revamping the whole winehq.com domain anyway due to > Corel's unfortunate demise ;-) > > Anyway, I'll be *really* glad once this finally gets done in a nice > solid timely cronjob. > > -- Andreas Mohr Stauferstr. 6, D-71272 > Renningen, Germany Tel. +49 7159 800604 > http://home.nexgo.de/andi.mohr/ > After checking winehq.com today I see that the online documentation is still not current. I also downloaded the sgml, pdf, and both htmls. They are still out of date. Now I realize that the staff at codeweavers are busy people but I would really like to see these up to date. Could I have some indication as to when this will done. Tony Lambregts Ps: I miss the network news service very much and want it to come back.

1 0

Has CVS access changed?
by Duane Clark 13 Mar '02

13 Mar '02

I just noticed that the patch I submitted is against an old version of CVS, even though I did the "cvs diff" today (3/13). Did I miss a change to the CVS configuration, perhaps in the move to the new server? I currently have .cvspass with :pserver:cvs@cvs.winehq.com:/home/wine Ah<Z

1 0

Re: Bug: fgets always reads from stdin
by Andriy Palamarchuk 13 Mar '02

13 Mar '02

Lawson, thank you very much for the help. lawson_whitney(a)juno.com wrote: > On Mon, 11 Mar 2002, Andriy Palamarchuk wrote: > > >>I'm trying to use function fgets, but it always reads >>from standard input. >> >> > I can't duplicate your results. [... skipped ...] As I found out I tried to feed 2 files to winemaker with -sym switches. Probably one of the files then was linked to Linux "fopen" function and returned FILE structure of incorrect format. Sorry to take your time. Andriy Palamarchuk __________________________________________________ Do You Yahoo!? Try FREE Yahoo! Mail - the world's greatest free email! http://mail.yahoo.com/

1 0

Re: Toolbar ReleaseCapture changes
by Duane Clark 13 Mar '02

13 Mar '02

These are comments about the patch that I submitted. Since it is a fairly significant change, and I don't yet have much of a track record (and am admittedly not a programmer by training or profession) I thought some detailed comments were in order. I have two applications, Xilinx fpga_editor and Actel designer, where the toolbars did not work. They were drawn fine, tooltips worked, and when clicked, they put messages into the status bar indicating what they were supposed to do. But the actual actions were never performed. Tracing the apps, I found that what was happening was that upon LBUTTONUP, the applications for whatever reason explicitly called ReleaseCapture() before TOOLBAR_LButtonUp() was executed. This caused TOOLBAR_LButtonUp() to be called with infoPtr->bCaptured == 0 and infoPtr->nButtonDown == -1, as would be expected. However, this also caused almost all of the code in the routine to be skipped, since most of it is contained within the large if(){} section. So I got ControlSpy and figured out how to get that to compile and run (under Borland C++Builder), and was able to modify it to explicitly call ReleaseCapture() before the TOOLBAR_LButtonUp(). This I did in the routine GetMsgProc() in ControlSpy, by testing for the correct hwnd and message before explicitely calling ReleaseCapture. I kind of expected CallWndProc() to be the right place, but it did not seem to be, and I really don't understand it well enough yet to know why. In any case, running this modified version (and the original version to compare results) under WinNT, I saw that the when ReleaseCapture is explicitely called before TOOLBAR_LButtonUp(), that all the same messages and notifications are still generated, with the exception that WM_CAPTURECHANGED does not get sent. And that is as expected, since it was already sent by the explicit call to ReleaseCapture(). So the patch modifies TOOLBAR_LButtonUp() to duplicate this behavior. It fixes both of the apps that were having the toolbar problem, and in the case of fpga_editor, it supports rebar and the toolbar continues to work. And I have tested it on a half dozen other apps, and all seem to be working fine.

1 0

wineconf: Call for meeting in the reception of respective hotel a t 7:30
by Patrik Stridvall 13 Mar '02

13 Mar '02

> -----Original Message----- > From: Dimitrie O. Paun [mailto:dpaun@rogers.com] [snip] > How do you plan on getting to the conference? Taxi, I guess, > in my case. Yes. > Maybe we should post to the list, I already did that, no reply. Trying again. :-) It seems that I was wrong earlier the last message from Cheryl Schwarzman said: "On Friday, a continental breakfast will be served complete with juice, coffee and muffins at 8:15." > and compile a list of > people with the > hotels they are staying at... I don't think we need to do anything that complicated. Why not just say that everybody regardless of hotel meet in or near the reception at 7:30 waiting there until 7:45 for people to show up. Identifing other people should be easy: Just ask anybody standing in or near the reception whether they are going to wineconf. Then we order enough taxis (or cabs I think people call then in the US) to carry us all to the conference. This would give us 30 minuter to wait for cabs and get to the conference which according to Michael Robertsson is 10 minutes away at least at the hotel I'm staying. I guess most other hotels is pretty close as well. The simple strategy is often the best.

1 0

The memory model
by Duane Clark 12 Mar '02

12 Mar '02

Over on comp.arch.fpga, there has been a discussion (in the thread "exceeding 2GB limits in xilinx") about the memory models of Windoze versus Linux, and whether running a Windows program under wine would impose the Windows memory model on an application. This all comes about because the newest Xilinx software says that to use their newest large devices, a computer needs a minimum of 3GB to run place and route! Apparently Windows allocates 2GB to user space and Linux allocates 3GB (just repeating what has been said by others there). It was mentioned that perhaps running the tools under Linux/wine might allow the tools to have access to the full 3GB available under Linux. In any case, this made me curious, and I was hoping some of the more knowledgable people here might be able to explain how this works under wine. Thanks, Duane

4 3

[wine-devel] WINE with Trad. Chinese input (XCin) Q2
by leanne 12 Mar '02

12 Mar '02

Dear all, My second question is about include/wnd.h The i18n35.udiff patch got the following segment: ~~~~~~~~~~~~~~~~~~~ --- 000928/include/win.h.org Fri Sep 15 05:42:53 2000 +++ 000928/include/win.h Mon Oct 2 12:16:03 2000 @@ -133,6 +133,9 @@ BOOL (*pSetHostAttr)(WND *, INT haKey, INT value); BOOL (*pIsSelfClipping)(WND *); void (*pSetWindowRgn)(WND *, const HRGN); + void (*pHideCaret)(WND *); + void (*pSetCaretPos)(WND *, INT, INT); + void (*pShowCaret)(WND *); } WND_DRIVER; extern WND_DRIVER *WND_Driver; ~~~~~~~~~~~~~~~~~~~ We cannot patch into the latest version of WINE because it does not have the following struct "tagWND_DRIVER" which is valid in 2000-09-09 release. If we do not patch it, any harm? Many thanks!! include/wnd.h (wine 2000-09-09 release) ============================================= typedef struct tagWND_DRIVER { void (*pInitialize)(WND *); void (*pFinalize)(WND *); BOOL (*pCreateDesktopWindow)(WND *, struct tagCLASS *, BOOL); BOOL (*pCreateWindow)(WND *, struct tagCLASS *, CREATESTRUCTA *, BOOL); BOOL (*pDestroyWindow)(WND *); WND* (*pSetParent)(WND *, WND *); void (*pForceWindowRaise)(WND *); void (*pSetWindowPos)(WND *, const WINDOWPOS *, BOOL); void (*pSetText)(WND *, LPCWSTR); void (*pSetFocus)(WND *); void (*pPreSizeMove)(WND *); void (*pPostSizeMove)(WND *); void (*pSurfaceCopy)(WND *, HDC, INT, INT, const RECT *, BOOL); void (*pSetDrawable)(WND *, HDC, WORD, BOOL); BOOL (*pSetHostAttr)(WND *, INT haKey, INT value); BOOL (*pIsSelfClipping)(WND *); void (*pSetWindowRgn)(WND *, const HRGN); } WND_DRIVER; extern WND_DRIVER *WND_Driver; ============================================= Cheers, Leanne Tsang

1 0

Re: More Shlwapi ordinal routines - updated
by Jürgen Schmied 12 Mar '02

12 Mar '02

Hello! I saw your patch today and noticed you are really doing W<-->A conversion for the version* functions. Is there a special reason for this? The A<-->W conversion in shlwapi is only for systems lacking the W-functions like win95 so it's not nessesary to do this for us. It's enough to just forward the entry points to the W-functions in the version.dll. Ciao Juergen -- just done a cvs update on my box after more than a year ;-) --- juergen.schmied(a)debitel.net

2 1

Only fixup borland imports once
by Uwe Bonnes 12 Mar '02

12 Mar '02

Changelog: loader/pe_image.c: PE_fixup_imports Only fixup Borland imports once. Some remarks in winnt.h make it resonable to use pe_imp->TimeDateStamp as marker This make the quicklogic suite crash later, after doing some real work. The dll causing the problems is netbios.dll from win95 osr2. Attention: I used diff -uw ,as I have heavily indented my code. -- Uwe Bonnes bon(a)elektron.ikp.physik.tu-darmstadt.de Free Software: If you contribute nothing, expect nothing -- Index: wine/loader/pe_image.c =================================================================== RCS file: /home/wine/wine/loader/pe_image.c,v retrieving revision 1.106 diff -u -w -r1.106 pe_image.c --- wine/loader/pe_image.c 2002/03/10 00:18:34 1.106 +++ wine/loader/pe_image.c 2002/03/12 00:01:45 @@ -344,6 +344,8 @@ } } else { /* Borland style */ TRACE("Borland style imports used\n"); + if (pe_imp->TimeDateStamp != -1) + { thunk_list = (PIMAGE_THUNK_DATA) RVA(pe_imp->FirstThunk); while (thunk_list->u1.Ordinal) { if (IMAGE_SNAP_BY_ORDINAL(thunk_list->u1.Ordinal)) { @@ -374,6 +376,8 @@ } thunk_list++; } + pe_imp->TimeDateStamp = -1; + } } } return 0;

1 0

RE: wineconf: Transport from the hotels to the conferance
by Patrik Stridvall 11 Mar '02

11 Mar '02

> Attendees are responsible for getting their persons from the hotel to > conference. Hopefully, it's a short cab ride or walk for > most. OK. I thought so. Just checking. > Coordinating > so that you carpool isn't such a bad idea. > > Conference starts at 9am. Feel free to show up at 8am for > coffee, juice and > donuts. And to help setup stuff. :^) > > It should take no longer than 10 minutes to get from Homestead to the > conference center. OK. So since the conferance is not providing REAL breakfast. How about for people at Homestead: 7.00 AM: Breakfast (at whatever place the hotel serves breakfast) 7.30 AM: Meeting for coordinating transport (at or near the hotel reception) Sounds good? PS. Everybody living at Homestead need not answer just to say yes. It is enough if a few do so the rest know that a least a few have agreed on when to meet.

1 0

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