Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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.
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.
Created attachment 1852 [details]
Thanks fro the patch