Closed toddsay closed 7 years ago
@toddsay I wasn't able to reproduce this issue (though I can kind of see where a problem could have happened). Can you try out this fix and make sure it resolves your issue?
Thanks @eamodio! The solution in your commit looks good, and I can confirm that it is working for me.
To clarify my original description, my scenario was:
This problem no longer occurs. 👍
@toddsay excellent -- thank you!
When making changes to existing tab groups and then exiting Visual Studio, those changes do not persist and are lost. The issue is that replacing data within the collection does not trigger collection change events. This change forces that notification to occur so that the changes are saved.