Changes between Version 3 and Version 4 of Ticket #3897, comment 16
- Timestamp:
- Jul 25, 2010, 9:35:39 AM (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #3897, comment 16
v3 v4 1 I took a closer look a nd the patch was treating the symptom. The problem is still caused by fItemsHeight not reaching 0 when all rows have been deleted. Yes it looks like the code will take care of it with two instances of "fItemsHeight -= subTreeHeight + 1;" but, unfortunately, the code doesn't operate like assumed.1 I took a closer look at Interface Kit and ColumnListView.cpp and the patch was treating the symptom. The problem is still caused by fItemsHeight not reaching 0 when all rows have been deleted. Yes it looks like the code will take care of it with two instances of "fItemsHeight -= subTreeHeight + 1;" but, unfortunately, the code doesn't operate like assumed. 2 2 3 3 In DriveSetup, let's say I have 3 volumes (parents), 2 with partition tables (children), for a total of 5 rows in the UI. That 5 UI rows (with two hideable/expandable) is only seen as 3 rows by the code.