[Mono-bugs] [Bug 82599][Wis] New - TreeView: no refresh when expand/collapse of off-screen node

[bugzilla-daemon at bugzilla.ximian.com]

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by andyhume32 at yahoo.co.uk.

http://bugzilla.ximian.com/show_bug.cgi?id=82599

--- shadow/82599	2007-08-26 06:28:19.000000000 -0400
+++ shadow/82599.tmp.31664	2007-08-26 06:28:19.000000000 -0400
@@ -0,0 +1,75 @@
+Bug#: 82599
+Product: Mono: Class Libraries
+Version: 1.2
+OS: 
+OS Details: XP SP2
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Wishlist
+Component: Windows.Forms
+AssignedTo: toshok at ximian.com                            
+ReportedBy: andyhume32 at yahoo.co.uk               
+QAContact: mono-bugs at ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: TreeView: no refresh when expand/collapse of off-screen node
+
+The TreeView display is not refreshed when the node being 
+expanded/collapsed is not in view when the action is carried out.  If one 
+then scrolls up/down over the 'out-of-date' nodes, the correct nodes are 
+drawn in their place.  Found on WinXP, SVN head.  (On 1.2.4_release a 
+whole worse behaviour occurs, where the whole view fills with the same 
+item; however it appears that this bug does not occur).
+
+
+With repro 2 from bug 81423, select "Childnode #39.4.1 Level 2", and 
+scroll it to the top line of the view (scroll -- here always means with 
+the mouse on the scrollbar).  When expanded see:
+#39.4.1/2, #39.4.1.0/3, #39.4.1.0.0/4, #39.4.1.0.1/4 and #39.4.1.1/3
+When collapsed see:
+#39.4.1/2, #39.4.2/2, #39.4.2.0/3, #39.4.2.0.0/4, #39.4.2.0.1/4
+
+* Collapse case
+Select "Childnode #39.4.1 Level 2", and make expanded.  Scroll it just 
+off the top of the window, ensuring it remains selected.
+
+Hit left-arrow or 'NumKeyPad-' to collapse.  Note that the screen does 
+not refresh.
+
+To double check that it has collapsed, bring it ("Childnode #39.4.1 Level 
+2") into view.  Note it has [+] so it *is* collapsed, but that it *still 
+has* viewable children.
+
+Now scroll it off the bottom of the display, and then back up.  Hurrah 
+the children have disappeared, and the next viewable node is "Childnode 
+#39.4.2 Level 2"
+
+* Expand case
+Select "Childnode #39.4.1 Level 2", and make it collapsed.  Scroll it 
+just off the top of the window (ensuring that the same node remains 
+selected).  (The in view nodes are "Childnode #39.4.2 Level 2" and its 
+children)
+
+Hit right-arrow to expand.  Note _no_ refresh -- we expected the screen 
+to fill with #39.4.1/2 children.
+
+To double check that it /has/ expanded, but only not refreshed, scroll it 
+("Childnode #39.4.1 Level 2") back into view.  Note it has [-] so it *is* 
+expanded, but it has *no* *displayed* children.
+
+Now scroll it off the bottom of the display, and then back up.  Hurrah, 
+the children have appeared.
+
+
+
+On 1.2.4_release things are even odder.  Things degenerate fast into a 
+situation where on scrolling the view fills with one item (the previous-
+top-most or previous-bottom-most item)!  That can happen even when 
+scrolling to prepare to run the tests above.  It can sometimes be 
+rectifying by clicking on each of the items/lines which causes the line 
+to refresh.
+
+In both the test cases above however the view does refresh correctly.  
+But on any scrolling the 'fill' effect occurs.