Shouldn't the header control resize itself? In this case the header control will now be unable to change its own size/width/position if it was used outside of the listview control. I would propose that doing the window change inside of HEADER_Layout or another function of the HEADER control would be more correct behavior. I'm curious as to your reasoning behind doing it this way. Thanks, Chris On Sun, 21 May 2000, Martin Fuchs wrote: > > Chris Morgan wrote: > > > I've been looking into why the listview control has no header in report > > styles and I've come across a patch that you sent in around April 28th > > or so. I was curious as to why you removed the MoveWindow() call > > inside of HEADER_Layout. > > Shouldn't the window be resized to match the size of its layout? If not a > > layout that specifies a larger window will result in a window that remains > > the same size. > > > > Thanks, > > Chris Morgan > > > Hi Chris! > > Of course the header control has be resized after calculating the layout. > But this should not be done directly in HEADER_Layout. Instead the > caller should use SetWindowPos() with the coordinates out of the > WINDOW_POS structure. I removed the MoveWindow() call because > it was marked as a "hack". However I did not notice that this was > needed to display the header control in list views. > > In the attachement you find a patch, which inserts the missing call to > SetWindowPos() in listview.c. With this change the header control is > visible again in list views with report style. > > > bye, > > Martin > > > ---------------------------------------- Content-Type: application/octet-stream; name="ListView-200005211316.diff" Content-Transfer-Encoding: quoted-printable Content-Description: ----------------------------------------
