May 2003 - Wine-devel - list.winehq.org

W95INF32.DLL added to wine
by Gerhard W. Gruber 10 May '03

10 May '03

I just sent the patch for adding the w95inf32 dll to the wine sources. I hope that the patch script is ok. I used diff -u for the tree, but I was not so sure about on how to do the new directory. I was following the instructions on WineHQ concerning the files, but it is nowhere mentioned if a new directory will be automatically created, so I trust this is enough. -- Gerhard Gruber Für jedes menschliche Problem gibt es immer eine einfache Lösung: Klar, einleuchtend und falsch. (Henry Louis Mencken)

1 0

NPTL auto detection
by Mike Hearn 10 May '03

10 May '03

Hi Alexandre, You said a few months ago Wine would soon detect whether to enable NPTL support at runtime rather than compile time. Presumably this will get in as part of the CodeWeavers merge. Do you know how long that might be? It seems every day people hit this problem and don't realise how to work around it. thanks -mike -- Mike Hearn <m.hearn(a)signal.qinetiq.com> QinetiQ - Malvern Technology Center

8 14

Progman DDE Server
by BiGgUn 10 May '03

10 May '03

Hi, While installing, mIRC 6.0.3 (evaluation), the installer was unable to create some links for mirc. I got the following error: err:ddeml:DdeConnect Done with INITIATE, but no Server window available Obviously, it seems that the required DDE server is not up and runnning. By enabling tracing on ddeml channel, i have found the queried server; it's Progman DDE server. On win2k (and other windows platforms i think), it seems that this server is launched when the system starts up or when a user logs in (i don't really know). Nevertheless, on wine this DDE server is not currently launched. Although, the progman application exists, is there a DDE server version already present in wine source tree ? Other question, when a program requires the Progman DDE server , should wine launch it automatically ? The DDE server would shutdown itself when the last wine instance exits. Is it possible to associate this DDE server with wineserver ? Stéphan

2 1

Re: Listview: Implemented Get/SetToolTips functions (rewrite)
by Dimitrie O. Paun 10 May '03

10 May '03

On May 10, 2003 03:51 am, BiGgUn wrote: > Hi, > > > > +static HWND LISTVIEW_SetToolTips( LISTVIEW_INFO *, HWND); > > > > I don't think you need these here. > > Dimitry, should i inline LISTVIEW_SetToolTips also ? Hey, my name is Dimitrie or Dimi :) > In this patch, LISTVIEW_SetToolTips is not inlined. No, that's fine, setters are not inlined currently. > static INT LISTVIEW_GetTopIndex(LISTVIEW_INFO *); > static BOOL LISTVIEW_EnsureVisible(LISTVIEW_INFO *, INT, BOOL); > static HWND CreateEditLabelT(LISTVIEW_INFO *, LPCWSTR, DWORD, INT, INT, INT, INT, BOOL); > +static HWND LISTVIEW_SetToolTips( LISTVIEW_INFO *, HWND); Why do you need this prototype here? I don't think it's needed, you don't use the function before the definition. > > +static HWND LISTVIEW_SetToolTips( LISTVIEW_INFO *infoPtr, HWND hwndNewToolTip) > +{ > + HWND hwndOldToolTip = infoPtr->hwndToolTip; Indentation seems to be hosed here, no? > + infoPtr->hwndToolTip = hwndNewToolTip; > + return hwndOldToolTip; > +} > + > /* LISTVIEW_SetUnicodeFormat */ > /* LISTVIEW_SetWorkAreas */ > > @@ -7214,7 +7241,7 @@ > GetWindowLongW(infoPtr->hwndHeader, GWL_STYLE) | HDS_HIDDEN); > } > } > - > + Please avoid such no-op changes, they make the patch longer for no good reason. I'm kinda picky, right? :) -- Dimi.

1 0

Re: Listview: Implemented Get/SetToolTips functions
by Dimitrie O. Paun 09 May '03

09 May '03

On May 9, 2003 02:45 pm, BiGgUn wrote: > static INT LISTVIEW_GetTopIndex(LISTVIEW_INFO *); > static BOOL LISTVIEW_EnsureVisible(LISTVIEW_INFO *, INT, BOOL); > static HWND CreateEditLabelT(LISTVIEW_INFO *, LPCWSTR, DWORD, INT, INT,INT, INT, BOOL); > +static HWND LISTVIEW_GetToolTips( LISTVIEW_INFO *); > +static HWND LISTVIEW_SetToolTips( LISTVIEW_INFO *, HWND); I don't think you need these here. > /******** Text handling functions *************************************/ > > @@ -5729,6 +5741,20 @@ > > /*** > * DESCRIPTION: > + * Returns tooltip associated to the listview > + * > + * PARAMETER(S): > + * [I] infoPtr : valid pointer to the listview structure > + * > + * RETURN: > + * Handle on listview tooltip > + */ > +static HWND LISTVIEW_GetToolTips( LISTVIEW_INFO *infoPtr) { > + return infoPtr->hwndToolTip; > +} Please just inline this one in the WinProc, the file is already too big and hard to maintain. > +/*** > + * DESCRIPTION: > + * Determines which listview item is located at the specified position. > + * > + * PARAMETER(S): > + * [I] infoPtr : valid pointer to the listview structure > + * [I] hwndNewToolTip : handle to new ToolTip > + * > + * RETURN: > + * old tool tip > + */ > +static HWND LISTVIEW_SetToolTips( LISTVIEW_INFO *infoPtr, HWND hwndNewToolTip) { Please follow the bracket convention used in the rest of the file. Indentation is currently mixed 2 or 4 space, please use 4 going forward. > + HWND hwndOldToolTip = infoPtr->hwndToolTip; > + infoPtr->hwndToolTip = hwndNewToolTip; > + return hwndOldToolTip; > +} Don't we need to do something with the new tool tip? I guess it's not part of this patch... :) > + /* init ToolTip */ > + infoPtr->hwndToolTip = NULL; Is this needed? Isn't the info structure initialized to 0? > > case LVM_GETTOOLTIPS: > - FIXME("LVM_GETTOOLTIPS: unimplemented\n"); > - return FALSE; > + return (LRESULT)LISTVIEW_GetToolTips(infoPtr); Yeah, just make this one: + return (LRESULT)infoPtr->hwndToolTip; -- Dimi.

1 0

int21 creat flags
by Ferenc Wagner 09 May '03

09 May '03

Hello, Is there any reason why Wine's implementation of DOS function 0x3c (create file with handle) explicitly ignores the invalid flag bits (volume label and directory)? NT4 returns error if any of these bits is set. Some PKSFX files have problem with this, since they try to create directories the invalid way (function 0x3c, flag=0x30, that is, archive directory), and they create FILES instead, which they can not cd later, of course... I was not able to find any information on possible extended use of the above function. So again, is there any reason why Wine does not conform the specification? Feri.

2 1

ALSA MIDI
by Jeff Smith 09 May '03

09 May '03

I am back from taking a break from Wine. Not that anyone noticed I was gone. :-) Before I took my break I had done some stuff locally for ALSA MIDI and DirectMusic. I see that some stuff has been done on DirectMusic in my absence, but I maybe I will still have something to contribute there. But in Eric Pouech's recent interview, he made mention that MIDI was still missing from the ALSA driver. I will submit what I can dig back up soon if nobody else is on the verge of submitting something. So speak now, or forever hold... nevermind. Hopefully I will be able to help out the Wine project some until the next time I will have to take a break (in September, when my daughter is due to be born). -- Jeff Smith __________________________________ Do you Yahoo!? The New Yahoo! Search - Faster. Easier. Bingo. http://search.yahoo.com

4 3

wine and accessibility
by KK singh 09 May '03

09 May '03

hi, I was trying to run accessibility enabled applications with wine. I was happy to find out that things like high contrast viewing and keyboard shortcuts seem to work fine. But screen readers like jaws fail. They seem to look for certain desktop api's Like OpenInputDesktop and OpenDesktop, which are stubs in wine. Is somebody out there working on "windows station and desktop api's" ? e.g. OpenInputDesktop() Or, Do an alternative way exists for screen readers on unix, and porting accessibility applications from windows is not worthwhile ?? Regards -kks ------------------------------------------- When thinking wont help, try twinking ;-) __________________________________ Do you Yahoo!? The New Yahoo! Search - Faster. Easier. Bingo. http://search.yahoo.com

2 1

Adding a new DLL question
by Gerhard W. Gruber 09 May '03

09 May '03

I now managed to get my DLL accepted by the wine framework. Now I wanted to know how it's best to proceed. Currently I have created the directories for w95inf32 with the spec file and a c file. I also added the directory to autoconf.ac and to dlls/Makefile.in so that it gets recogniced by wine. The c file is currently empty and contains only the skeleton of the exported functions from the DLL. Shall I submit this already to wine or is it prefered that I try to add some functionality first? I don't know how long it will take until I can get some working code on this because I need to reverse engineer the code. I haven't found any usefull information about the exported functions so far. -- Gerhard Gruber Für jedes menschliche Problem gibt es immer eine einfache Lösung: Klar, einleuchtend und falsch. (Henry Louis Mencken)

2 1

SMapLS_IP_EBP question
by Gerhard W. Gruber 09 May '03

09 May '03

In a DLL I looked into the exported function calls SMapLS_IP_EBP/SUnmapLS_IP_EBP. I noticed that these functions are implemented in wine/memory.c (if I remember correctly), but I haven't found any code in wine that references this functions. Now I wonder why. These functions deal with linear/segmented pointers which I suppose are used for 32/16 Bit transition. The DLL has two implementations one for 32 and one for 16 Bit and I assume that the 32 Bit version uses code from the 16 Bit code. I guess that there are other DLLs where the same would be true, so I would expect that other DLL implementations also call these functions (at least in the original version). Since there are no calls in wine to this functions, does this mean that this can be ignored because it is an implementation detail? But then how is the code handled in 16Bit environment? -- Gerhard Gruber Für jedes menschliche Problem gibt es immer eine einfache Lösung: Klar, einleuchtend und falsch. (Henry Louis Mencken)

2 1