wine-devel

wine-devel@winehq.org

12 participants
84463 discussions

RE: Re:can windows be reparented?
by Medland, Bill 15 Aug '02

15 Aug '02

> -----Original Message----- > From: Dmitry Timoshkov [mailto:dmitry@baikal.ru] > Sent: Thursday, August 15, 2002 10:00 AM > To: Medland, Bill > Cc: wine-devel(a)winehq.com > Subject: Re: Re:can windows be reparented? > > > "Medland, Bill" <Bill.Medland(a)accpac.com> wrote: > > > (Do you want the test case code?) > > Why not? :-) > > -- > Dmitry. > > > First is without WS_POPUP, second is with

1 0

RE: Re:can windows be reparented?
by Medland, Bill 15 Aug '02

15 Aug '02

> -----Original Message----- > From: Dmitry Timoshkov [mailto:dmitry@baikal.ru] > Sent: Thursday, August 15, 2002 9:17 AM > To: Medland, Bill > Cc: wine-devel(a)winehq.com > Subject: Re: Re:can windows be reparented? > > > "Medland, Bill" <Bill.Medland(a)accpac.com> wrote: > > > Honest question : how do you know the parent is changing? > by calling > > GetWindowLong (GWL_HWNDPARENT)? > > Yes, and verifying the result in Spy++. (As discussed in my other email) I guess Spy++ is displaying the result of GetWindowLong > > > I believe that it is the owner that is changing and the > parent (as returned > > by getAncestor (GA_PARENT) willl be unchanged. > > Hmm, I didn't try GetAncestor(), only GetWindowLong() and GetParent(). (Do you want the test case code?) > > -- > Dmitry. > > >

2 1

RE: Re:can windows be reparented?
by Medland, Bill 15 Aug '02

15 Aug '02

> -----Original Message----- > From: Dmitry Timoshkov [mailto:dmitry@baikal.ru] > Sent: Tuesday, August 13, 2002 6:33 PM > To: us(a)the-edmeades.demon.co.uk > Cc: wine-devel(a)winehq.com > Subject: Re: Re:can windows be reparented? > snip > 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). Honest question : how do you know the parent is changing? by calling GetWindowLong (GWL_HWNDPARENT)? I believe that it is the owner that is changing and the parent (as returned by getAncestor (GA_PARENT) willl be unchanged. snip Bill

2 1

Some observations on window parentage etc.
by Medland, Bill 15 Aug '02

15 Aug '02

Here are some observations with regard to Window parentage/ownership etc. Clearlt Microsoft documentation is quite out of date and contradictory on the subject these days so we are going to have to experiment and find out what actually happens. We also are going to have to be careful about terminology and not jumping to conclusions. I mean what ther heck are we supposed to think when Spy++ shows a window as a top-level window (by which I mean just below the desktop in the listview that Spy++ uses), tells us that its parent is its owner (a different top-level window) but that "parent" says it has no children. So. 1. GetParent does not necessarily return the same value as GetWindowLong (GWL_HWNDPARENT). I have seen GetParent returning 0 while GetWindowLong returns the same non zero value as GetWindow (GW_OWNER). 2. GetAncestor (GA_PARENT) seems to be the best way to get the "true parent". 3. WIN_CreateWindowEx is currently slightly wrong. I know MSDN says don't mix WS_POPUP and WS_CHILD but if you do then the result is wrong, I believe. However I am loth to fix it and submit the patch because that really messes everything else up so I guess we need a bigger patch first. (Heck, even under windows 98 you can get the kernel to fall over rather easily this way). 4. I don't like the look of GetAncestor (GA_ROOTOWNER). The MSDN documentation suggests that it should return the result of recursively calling GetParent (or should it be recursively calling GetWindowLong (GWL_HWNDPARENT) whereas GetAncestor (GA_ROOT) should return the result of recursively calling GetAncestor (GA_PARENT) (each stopping just before the desktop, of course). (And of course that is definition, not necessarily mechanism) More to follow. Bill

1 0

RE: what's with WS_OVERLAPPED?
by Medland, Bill 15 Aug '02

15 Aug '02

> -----Original Message----- > From: Ove Kaaven [mailto:ovehk@ping.uio.no] > Sent: Wednesday, August 14, 2002 11:08 AM > To: Medland, Bill > Cc: Wine devel (E-mail) > Subject: Re: what's with WS_OVERLAPPED? > > > > On Wed, 14 Aug 2002, Medland, Bill wrote: > > > (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? > > WS_OVERLAPPED is in practice considered the absence of the > WS_POPUP and > WS_CHILD flags, I believe. > Thanks Ove; that'll do for a working hypothesis. (I wish Microsoft would be consistant) Just for the record it is clearly more complex than that. I guess since Microsoft wrote it we can trust Spy++ a little. I have seen spy++ declare that a "tooltips" class window (style 0x84800000/00000088) has style WS_OVERLAPPED whereas a "tooltips_class32" class window (style 0x84800003/00000088) doesn't. Bill

1 0

ListView Patch
by Steve Whine 15 Aug '02

15 Aug '02

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 14 Aug '02

14 Aug '02

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 14 Aug '02

14 Aug '02

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 14 Aug '02

14 Aug '02

(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 14 Aug '02

14 Aug '02

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

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