User (Old forums)MemberFebruary 6, 2008 at 6:24 pmPost count: 23064
When I scroll the grid to the bottom most, only one line can be seen. Actually, I think it’s better to make the grid filling with rows even if it is scrolled to the bottom most. Or maybe anybody know a property to control this? Thanks
Imported from legacy forums. Posted by Henry (had 2657 views)Xceed SupportMemberFebruary 7, 2008 at 8:20 amPost count: 5658
This is by design and is required by the fact that, in WPF, a DataRow could take any form, layout or size.
To be ensured that the desired row would always be visible in the page, the most versatile solution was to always make sure it was the “first” visible row.
Now, this has the side effect that one could scroll the grid in such a way that only the last item is visible at the top.
We are aware that this situation is less than perfect and are considering alternate solutions.
Imported from legacy forums. Posted by Marcus [Xceed] (had 486 views)User (Old forums)MemberFebruary 7, 2008 at 10:12 amPost count: 23064
Marcus, thank you for your response. I can understand this situation now.
Imported from legacy forums. Posted by Henry (had 2997 views)User (Old forums)MemberApril 29, 2010 at 9:37 amPost count: 23064
Has any recent release or update changed this behavior? If not, is there anyway to stop this from happening (i.e., code)? Our users would like us to stop showing the last row at the top as described in this issue thread.
Imported from legacy forums. Posted by Gord (had 283 views)Odi [Xceed]SpectatorApril 29, 2010 at 11:28 amPost count: 426
I seem to recall this issue being fixed — checking in the latest online demo, scrolling to the end of the grid always shows all the rows.
Imported from legacy forums. Posted by Odi [Xceed] (had 357 views)User (Old forums)MemberApril 29, 2010 at 11:32 amPost count: 23064
Thank you for the update!
Imported from legacy forums. Posted by Gord (had 361 views)User (Old forums)MemberApril 30, 2010 at 9:21 amPost count: 23064
This behavior has not changed. I tried the latest release. Would anyone be able to suggest a work-around for this behavior (xaml and/or c#)?
Imported from legacy forums. Posted by Gord (had 538 views)
- You must be logged in to reply to this topic.