- Wine-Devel - list.winehq.org

ListView Patch
by Steve Whine Aug. 15, 2002

Aug. 15, 2002

Hi all, I should maybe have posted this to the patches list, but I would like your comments first. I have fixed a few problems with the ListView control when using icons larger than the sizes returned by the system metrics. This (attached) patch also causes LISTVIEW_Arrange (which was previously a stub) to call the LISTVIEW_AlignTop/Left when appropriate. Please let me know what you think. This is my first time doing any of this, so let me know what I'm doing wrong/right. Cheers Steve

1 0

ListView Issues
by Steve Whine Aug. 14, 2002

Aug. 14, 2002

Hi, I've just started looking into getting a project of wine running on Linux via Wine, and I'm very impressed so far! However, there are a few (mostly minor) problems with the ListView control: - When using icons bigger than the sizes returned by SystemParametersInfo(SPI_GETICONMETRICS), the text for the items is not displayed correctly at the bottom of the icon. - When running a program created by C++ Builder 5, clicking on an item in the listview causes an access violation in C++ Builder's VCL library code - it is obviously getting passed an unexpected value. - The amount of text displayed is often far less than is displayed in Windows, making the listbox difficult to use. I have been looking into the ListView code and have hacked a fix for the first and third problem, but I am having a little difficulty understanding the code - the LISTVIEW_INFO struct has both an nItemWidth/nItemHeight pair describing the width/height of each item, and an iconSpacing SIZE struct that seems to do the same. What is the difference in these, where should one be used and where should the other be used? Is anyone actively maintaining the listview code, or should I just carry on hacking until I'm happy with it, and post the changes here? I have created a small test program to demonstrate these problems which I can post if anyone is interested. I must say it's very nice to be able to wade into the code to fix these problems myself rather than waiting for someone else (not) to do it! Cheers Steve __________________________________________________ Do You Yahoo!? Everything you'll ever need on one web page from News and Sport to Email and Music Charts http://uk.my.yahoo.com

3 2

Re: New Slovak translation
by Vincent Béron Aug. 14, 2002

Aug. 14, 2002

Le lun 12/08/2002 à 08:35, Andrej Kruták a écrit : > > [snip] > > PS3: What about documentation. Are you going to write also some desc. > of > WinAPI or not? I know there's MSDN, but not everyone can subscribe > it... > At least basic things like file IO, windowing, you know :) I have some > experiences with this, so I could help... The documentation on http://msdn.microsoft.com is quite accessible. If you know on which API you want some info, just type it's name in the search box, and you'll get a bunch of results. In my experience, some of the top results are often about WinCE, just skip them. Vincent

1 0

what's with WS_OVERLAPPED?
by Medland, Bill Aug. 14, 2002

Aug. 14, 2002

(Regarding the whole issue of windows reparenting) MSDN keeps going on about windows with the WS_OVERLAPPED style. However surely (since WS_OVERLAPPED=0) every window has such a style these days. Is there something I don't understand? Bill

2 1

Re: RESUBMIT: Quicken 2000 bug/Category blanking => Wine patch
by Dimitrie O. Paun Aug. 14, 2002

Aug. 14, 2002

On August 14, 2002 01:53 pm, Carl Sopchak wrote: > It was suggested to me that I should not use strlen(), since I'm not > positive if the string will ever really terminate (which may cause a seg > fault), so I programmed my own scan for a null character.. > > Here's the revised patch (attached). What about this: --- controls/edit.c 13 Jun 2002 19:20:43 -0000 1.95 +++ controls/edit.c 14 Aug 2002 17:49:13 -0000 @@ -3957,20 +3957,25 @@ */ static INT EDIT_WM_GetText(EDITSTATE *es, INT count, LPARAM lParam, BOOL unicode) { + INT ii; + if(!count) return 0; if(unicode) { LPWSTR textW = (LPWSTR)lParam; strncpyW(textW, es->text, count); - textW[count - 1] = 0; /* ensure 0 termination */ + for (ii = 0; (ii < count) & textW[ii]; i++) ; + textW[ii - 1] = 0; /* force 0 termination */ return strlenW(textW); } else { LPSTR textA = (LPSTR)lParam; WideCharToMultiByte(CP_ACP, 0, es->text, -1, textA, count, NULL, NULL); - textA[count - 1] = 0; /* ensure 0 termination */ + for (ii = 0; (ii < count) & textA[ii]; i++) ; + textA[ii - 1] = 0; /* force 0 termination */ return strlen(textA); } } Untested :) -- Dimi.

1 0

Am I the only one getting replies from RealNetworks?
by Medland, Bill Aug. 14, 2002

Aug. 14, 2002

I am getting messages from RealNetworks corresponding to each of my posts to wine-devel. I presume "Mysore Jaisimha" is on the mailing list but no longer works there. Can we do anything about it or do I just throw the messages away? Bill

2 1

RE: Re:can windows be reparented?
by Medland, Bill Aug. 14, 2002

Aug. 14, 2002

> -----Original Message----- > From: Dmitry Timoshkov [mailto:dmitry(a)baikal.ru] > Sent: Wednesday, August 14, 2002 9:34 AM > To: Medland, Bill > Cc: wine-devel(a)winehq.com > Subject: Re: Re:can windows be reparented? > > > keep cc'ing wine-devel please Sorry; I just realised. It's the way I have Outlook set up; I get confused. > > "Medland, Bill" <Bill.Medland(a)accpac.com> wrote: > > > > Could you please test patch posted by Bill Medland to > > > wine-patches today? It's > > > not entirely correct though. My tests show that > > > SetWindowLong(GWL_HWNDPARENT) > > > call changes simultaneously both parent and owner for top > > > level windows and > > > returns old value (not sure old owner or parent it is). > > > > Even if the window is not in fact a child? > > Yes. According to my test program. > > > Please excuse my ignorance here; > > I am still a little shaky on terminology. Surely if it is > a top level > > window then its parent is the desktop and always will be. > > > > Or are you saying that it reparents to the desktop (and so > the problem is > > down in the SetParent code)? > > I don't see a reparenting to desktop in the relay trace. > > > > But top level windows created by Visual Vasic are special: > > > they have no parent, > > > but only owner according to Spy++. In my tests I can't > > > reproduce it yet. > > > > So you suspect that Spy++ is not telling the truth? (It > wouldn't be the > > first time) > > I incline to trust Spy++ here. It correctly shows paerent/owner for my > test application playing with SetParent/SetWindowLong. It seems that > Windows always sets 0 in the parent field if the parent is > desktop. Even > after explicit SetParent(GetDesktopWindow()) or > SetWindowLong(GWL_HWNDPARENT, > GetDesktopWindow()) GetWindowLong(GWL_HWNDPARENT)/GetWindow(GW_OWNER) > return 0 in my tests. > > > > A bit of investigation of Wine source revealed that some > places use > > > GetAncestor(hwnd, GA_PARENT), while others use GetParent(hwnd). > > > > And, in the case of WIN_CreateWindowEx, GetAncestor (hwnd, GA_ROOT) > > > > > Since > > > their behaviour is different in respect of top level and > > > child windows, > > > some major clean up in that area in Wine is needed. > > > > Careful. > > > > In our particular case, according to Spy++ the owner of the > ThunderRT6FormDC > > is a third-generation window. viz. the actual window > requested, not one of > > its ancestors. > > > > i.e. I see the call to SetWindowLong (30056 (The > ThunderRT6FormDC), -8, > > 10046 (The ThunderRT6UserControlDC)) > > > > I guess an important point here is that in our case the > Visual Basic is an > > OCX sitting inside a container and so the > ThunderRT6UserControlDC is not > > first generation. > > Now I don't understand your terminology. parent - child - sibling are > the termings in the Windows world. Who of them was born > earlier matters > only when Z order and visibility are taken into account (and > can be easily > changed). Sorry; I am being unclear. I mean that (statically, according to Spy++, when the popup form is active) 1. The ThunderRT6FormDC which "is" the form has style WS_OVERLAPPED, no parent (i.e. the desktop) and owner is the ThunderRT6UserControlDC 2. The ThunderRT6UserControlDC which, I believe, "is" the ocx, has style WS_OVERLAPPED and no owner, but its parent is an ATL window 3. That ATL window's parent is another ATL window 4. That second ATL window has no parent. (So, by generations I am talking about the static parent relationship, independent of how it came to be; c.f. old people adopting young ones resulting in skipped generations) > > -- > Dmitry. > > > And I have just noticed the lie in MSDN. It says (Platform SDK - Windows User Interface - Owned windows) that once the window has been created, with an owner, you cannot change the owner. That has to be wrong. A propos. I think there is a related error in CreateWindowEx. At least it disagrees with MSDN. If passed a parent If this is a child set parent to the paremt passed in and leave the owner 0 else set the parent to the desktop and the owner to the GA_ROOT ancestor of the window passed in. Surely it should be (according to MSDN) if passed a parent if style includes WS_OVERLAPPED or WS_POPUP assert style does not include WS_CHILD if the parent is itself WS_OVERLAPPED or WS_POPUP parent is desktop and owner is the parent passed in else if the parent is a WS_CHILD then parent is desktop and owner is the GetAncestor(parent, GA_ROOT) else assert false? else assert WS_CHILD owner is 0 and parent is as specified Comments? One datum of use. In our particular case this fits; the ThunderRT6FormDC is WS_OVERLAPPED with no parent. Its owner is the ThunderRT6UserControlDC which also is WS_OVERLAPPED but has a parent. Bill

1 0

Re: CVS not building?
by jhurst＠ii.net Aug. 14, 2002

Aug. 14, 2002

I'm *really* sorry about the multiple messages! :( It seemed I jumped the gun and a manual removal of what i thought were problematic .o files did not resolve my build error! :( -jan On Thu, 2002-08-15 at 00:54, jhurst(a)ii.net wrote: > Hello, > > I just updated my CVS tree, and as several files seemed to have been > updated since my last CVS update I attempted to build a new wine. The > build fails with the error attached below. > > My questions are: > > 1. what is the "correct" way to (re)build wine when an existing wine has > previously been built? I have used ./tools/wineinstall previously (and > the attached error is a result). Is this correct? > > 2. Is there a problem with the files I have just pulled from CVS or have > I broken something on this end?! > > Regards, > > -jan > jhurst(a)ii.net > > --> snip <-- > make[2]: Entering directory `/usr/src/wine/dlls/urlmon' > LD_LIBRARY_PATH="../../library:../../unicode:$LD_LIBRARY_PATH" > ../../tools/winebuild/winebuild -fPIC -D__WINE__ -o urlmon.spec.c -spec > ./urlmon.spec urlmon.dll.tmp.o -L../../dlls -lole32 -lwininet -luser32 > -lkernel32 > ./urlmon.spec:1: could not open .so file for wininet.dll > make[2]: *** [urlmon.spec.c] Error 1 > make[2]: Leaving directory `/usr/src/wine/dlls/urlmon' > make[1]: *** [urlmon] Error 2 > make[1]: Leaving directory `/usr/src/wine/dlls' > make: *** [dlls] Error 2 > --> snip <--

1 0

Re: CVS not building?
by jhurst＠ii.net Aug. 14, 2002

Aug. 14, 2002

My apologies. It seems make clean did not remove some .o files. Manual removal has allowed me to continue the build process. However, can someone please answer my first question? Regards, -jan On Thu, 2002-08-15 at 00:54, jhurst(a)ii.net wrote: > Hello, > > I just updated my CVS tree, and as several files seemed to have been > updated since my last CVS update I attempted to build a new wine. The > build fails with the error attached below. > > My questions are: > > 1. what is the "correct" way to (re)build wine when an existing wine has > previously been built? I have used ./tools/wineinstall previously (and > the attached error is a result). Is this correct? > > 2. Is there a problem with the files I have just pulled from CVS or have > I broken something on this end?! > > Regards, > > -jan > jhurst(a)ii.net > > --> snip <-- > make[2]: Entering directory `/usr/src/wine/dlls/urlmon' > LD_LIBRARY_PATH="../../library:../../unicode:$LD_LIBRARY_PATH" > ../../tools/winebuild/winebuild -fPIC -D__WINE__ -o urlmon.spec.c -spec > ./urlmon.spec urlmon.dll.tmp.o -L../../dlls -lole32 -lwininet -luser32 > -lkernel32 > ./urlmon.spec:1: could not open .so file for wininet.dll > make[2]: *** [urlmon.spec.c] Error 1 > make[2]: Leaving directory `/usr/src/wine/dlls/urlmon' > make[1]: *** [urlmon] Error 2 > make[1]: Leaving directory `/usr/src/wine/dlls' > make: *** [dlls] Error 2 > --> snip <--

1 0

Re: Re:can windows be reparented?
by Dmitry Timoshkov Aug. 14, 2002

Aug. 14, 2002

keep cc'ing wine-devel please "Medland, Bill" <Bill.Medland(a)accpac.com> wrote: > > Could you please test patch posted by Bill Medland to > > wine-patches today? It's > > not entirely correct though. My tests show that > > SetWindowLong(GWL_HWNDPARENT) > > call changes simultaneously both parent and owner for top > > level windows and > > returns old value (not sure old owner or parent it is). > > Even if the window is not in fact a child? Yes. According to my test program. > Please excuse my ignorance here; > I am still a little shaky on terminology. Surely if it is a top level > window then its parent is the desktop and always will be. > > Or are you saying that it reparents to the desktop (and so the problem is > down in the SetParent code)? I don't see a reparenting to desktop in the relay trace. > > But top level windows created by Visual Vasic are special: > > they have no parent, > > but only owner according to Spy++. In my tests I can't > > reproduce it yet. > > So you suspect that Spy++ is not telling the truth? (It wouldn't be the > first time) I incline to trust Spy++ here. It correctly shows paerent/owner for my test application playing with SetParent/SetWindowLong. It seems that Windows always sets 0 in the parent field if the parent is desktop. Even after explicit SetParent(GetDesktopWindow()) or SetWindowLong(GWL_HWNDPARENT, GetDesktopWindow()) GetWindowLong(GWL_HWNDPARENT)/GetWindow(GW_OWNER) return 0 in my tests. > > A bit of investigation of Wine source revealed that some places use > > GetAncestor(hwnd, GA_PARENT), while others use GetParent(hwnd). > > And, in the case of WIN_CreateWindowEx, GetAncestor (hwnd, GA_ROOT) > > > Since > > their behaviour is different in respect of top level and > > child windows, > > some major clean up in that area in Wine is needed. > > Careful. > > In our particular case, according to Spy++ the owner of the ThunderRT6FormDC > is a third-generation window. viz. the actual window requested, not one of > its ancestors. > > i.e. I see the call to SetWindowLong (30056 (The ThunderRT6FormDC), -8, > 10046 (The ThunderRT6UserControlDC)) > > I guess an important point here is that in our case the Visual Basic is an > OCX sitting inside a container and so the ThunderRT6UserControlDC is not > first generation. Now I don't understand your terminology. parent - child - sibling are the termings in the Windows world. Who of them was born earlier matters only when Z order and visibility are taken into account (and can be easily changed). -- Dmitry.

1 0