Bug 5010 - removing an expanded TreeNode from a TreeView results in an invalid selection
Summary: removing an expanded TreeNode from a TreeView results in an invalid selection
Status: RESOLVED FIXED
Alias: None
Product: Class Libraries
Classification: Mono
Component: Windows.Forms ()
Version: 2.10.x
Hardware: PC Linux
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2012-05-10 15:29 UTC by Stephen McConnel
Modified: 2012-05-19 00:51 UTC (History)
2 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:


Attachments
sample program to demonstrate the bug (6.98 KB, application/x-gzip)
2012-05-10 15:29 UTC, Stephen McConnel
Details
proposed patch (740 bytes, patch)
2012-05-10 15:38 UTC, Stephen McConnel
Details


Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on GitHub or Developer Community with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED FIXED

Description Stephen McConnel 2012-05-10 15:29:33 UTC
Created attachment 1851 [details]
sample program to demonstrate the bug

If an expanded TreeNode is removed from a TreeView, its first child is chosen as the new selected node.  This is obviously incorrect.

The most common user experience would just be losing any indication of a selected node.  However, in the program I'm working on, a crash results pretty easily.

In the attached sample program, Duplicate one of the complex nodes (or instance "Variant Forms"), then Remove it immediately.  A message box should pop up to inform you that the current node is now invalid.
Comment 1 Stephen McConnel 2012-05-10 15:38:02 UTC
Created attachment 1852 [details]
proposed patch
Comment 2 Miguel de Icaza [MSFT] 2012-05-19 00:51:18 UTC
Thanks fro the patch