I'm trying to track down an index out of range bug deep within your control so I decided to whip up a demo to send to you guys as something is off.
Setup1. TileView is bound to a collection in ViewModel2. Button in header with the TAG bound to the object in the collection once clicked removes the object from the collection3. MaxMaximzedTiles = Collection.Count (gives a cool effect)bug 1: Imagine a 3 column layout. Move col 2 to col 1 and click the remove button in col 2. This removes the wrong tile pane.bug 2: With all tile panes maximized clicking remove does some wacky things and starts to minimize panels.Adding a close button is a MUST for us.
-Mark
[EDIT]: I unchecked KeepMaximizedTileInCurrent... and my index out of range bug went a way and bug: 2 appears to have gone away. Bug 1 still exists however.
Hi Mark,Thanks for this post.We are working to fix the first issue.About the second one - you don't need to set MaxMaximizedTiles when remove some tile or you must call UpdateLayout before decrease the number of maximized tiles:_ViewModel.Widgets.Remove(widget);TileView.UpdateLayout();TileView.TilePanelSettings.MaxMaximizedTiles = _ViewModel.Widgets.Count;Regards,Marin