I am investigating a weird scrolling behavior in our app, I have more or less reproduced it in the attached sample app. I say 'more or less' because the little sample doesn't exactly have the same structure as our app but the result looks to be the same as what is happening in our software.
When declaring an unnamed style that targets the RadTileViewItem, scrolling the minimized TileViewItems while have one in the Maximized state, reverts all the minimized ones to their 'Normal' state as well as the one that was maximized. If the RadTileViewItem style is given a Key in the resource dictionary and used explicitly in the TileView's ItemContainerStyle property the scrolling works fine.
Both ways of using the style should, in my opinion, behave exactly the same.
Please take a look.
The values are switched. NewState holds the value of OldState. OldState holds the value of NewState
When you add RadBook as a content of RadTileViewItem and reorder the TileViewItem you get ArgumentOutOfRangeException. Workaround: You can set the width of the RadBook.
In application with heavier styles and a slower machine when items are dragged and swiped it sometimes leads to exception: Cannot animate the 'VerticalOffset' property on a 'Telerik.Windows.Controls.TileViewPanel' using a 'System.Windows.Media.Animation.DoubleAnimationUsingKeyFrames'
Then the FlowDirection is set to RightToLeft and you start dragging an RadTileViewItem it looks flipped.
When we have enough items so that the vertical scroll bar is displayed and then remove such amount of items so that they have enough space to fit in their container (and scrollbar is not needed) the vertical scrollbar is still visible.
DragAndDrop doesn't work in RadTileView on Mac OS with elevated trust and out of browser application
Allow users to dynamically change the DraggingItem
TextBox (or input control) is in LargeContent of FluidContentControl in RadTileViewItem. Validation fails and Red border is shown on the TextBox. TileState is changed then it is Maximized again. Validation fails again but no red border is shown.
Provide support for changing the ItemContainerStyleSelector runtime.
InvalidOperationException in thrown in design time in certain situations
The Header of the TileViewItems is bound only for the first X tiles, where X is the loadsize of the VirtualQueryableCollectionView
Implement command support for events like TileStateChanged. Allow sending the TileItem, which state is changing, as an argument.
Implement a mouse wheel support for the Horizontal ScrollBars of the control