I have a RadTileView whose ItemsSource is an ObservableCollection of a class.
Say I populate the collection with 9 items and set the Colums to 3 and set the RowHeight to a set size (giving the scroll). This results in a 3x3 RadTileView. Now, starting in the upper right and reading by rows, the first five tiles are "unlocked" (OnPreviewPositionChanged sets e.Handled to false) and the last four are "locked" (e.Handled is set to true). When one of the items in the RadTileView ItemsSource collection is removed (MyCollection.Remove(MyClassObject), the unlocked tiles rearrange themselves but the locked ones will not. This leaves ugly gaps in the grid that do not behave well when maximizing and minimizing. The wrong tile will maximize when you try to maximize a tile below the gap.
Is this a known issue? Is there a work-around besides repopulating the collection completely? My tile views contain some slow-performing RadCharts and refreshing all of them when the user removes one tile is an unacceptable user experience. I also tried flagging the RadTileView before and after the item remove so that I could read the flag in OnPreviewPositionChanged, but I ran into very complex problems that I think may be thread safety issues, so I'm hoping someone can provide a more straight-forward solution.
Thanks.
- Thomas.
Say I populate the collection with 9 items and set the Colums to 3 and set the RowHeight to a set size (giving the scroll). This results in a 3x3 RadTileView. Now, starting in the upper right and reading by rows, the first five tiles are "unlocked" (OnPreviewPositionChanged sets e.Handled to false) and the last four are "locked" (e.Handled is set to true). When one of the items in the RadTileView ItemsSource collection is removed (MyCollection.Remove(MyClassObject), the unlocked tiles rearrange themselves but the locked ones will not. This leaves ugly gaps in the grid that do not behave well when maximizing and minimizing. The wrong tile will maximize when you try to maximize a tile below the gap.
Is this a known issue? Is there a work-around besides repopulating the collection completely? My tile views contain some slow-performing RadCharts and refreshing all of them when the user removes one tile is an unacceptable user experience. I also tried flagging the RadTileView before and after the item remove so that I could read the flag in OnPreviewPositionChanged, but I ran into very complex problems that I think may be thread safety issues, so I'm hoping someone can provide a more straight-forward solution.
Thanks.
- Thomas.