Duane Clark wrote:
While the MSDN specifically says that column zero should not be deleted, it does in fact work on WinNT, and at least one app depends on it. On WinNT, deleting column zero deletes the last column of items but the first header. Since no app will ever depend on that bizarre behavior, we just delete the last column including the header.
I probably should have mentioned why the app deletes column zero. It repeatedly deletes column zero, testing the returned Boolean until it gets false, and then it starts inserting new columns. So it ends up completely replacing the listview contents.
On February 13, 2003 11:06 pm, Duane Clark wrote:
I probably should have mentioned why the app deletes column zero. It repeatedly deletes column zero, testing the returned Boolean until it gets false, and then it starts inserting new columns. So it ends up completely replacing the listview contents.
That sounds ... strage <g>. Why not just use LVM_DELETEALLITEMS?
Dimitrie O. Paun wrote:
On February 13, 2003 11:06 pm, Duane Clark wrote:
I probably should have mentioned why the app deletes column zero. It repeatedly deletes column zero, testing the returned Boolean until it gets false, and then it starts inserting new columns. So it ends up completely replacing the listview contents.
That sounds ... strage <g>. Why not just use LVM_DELETEALLITEMS?
Well, I thought it seemed a bit strange too. The short answer is that the new listview has a different number of columns.
-
Dimitrie O. Paun -
Duane Clark