Row indicator arrow does not mark selected rows

6 posts, 0 answers
  1. ClausDC
    ClausDC avatar
    65 posts
    Member since:
    Feb 2010

    Posted 17 Nov 2010 Link to this post

    For a few older version and now in the Q3 release the row indicator arrow does not move to highlight the selected row anymore (see attached image), it remains static in the first row. What am I missing here?

    Thanks.
  2. Vlad
    Admin
    Vlad avatar
    11100 posts

    Posted 17 Nov 2010 Link to this post

    Hello,

     You can set IsSynchronizedWithCurrentItem to true to fix this. 

    Kind regards,
    Vlad
    the Telerik team
    See What's New in RadControls for WPF in Q3 2010 on Tuesday, November 16, 2010 11:00 AM - 12:00 PM EST or 10:00 PM - 11:00 PM EST: Register here>>
  3. ClausDC
    ClausDC avatar
    65 posts
    Member since:
    Feb 2010

    Posted 17 Nov 2010 Link to this post

    That was quick, I will try this!

    Thanks you!
  4. ClausDC
    ClausDC avatar
    65 posts
    Member since:
    Feb 2010

    Posted 17 Nov 2010 Link to this post

    This works!

    Bonus question: What is the difference between CurrentItem and SelectedItem?
  5. Carlos Alberto
    Carlos Alberto avatar
    12 posts
    Member since:
    Apr 2014

    Posted 30 Jul 2014 Link to this post

    Hello, I established a true IsSynchronizedWithCurrentItem but rowindicator appears in each row selected, how do I show it only in that is currently selected?
  6. Boris
    Admin
    Boris avatar
    276 posts

    Posted 31 Jul 2014 Link to this post

    Hello Carlos,

    I have just replied to your Show multiple rowindicators forum thread. In order to avoid double posting, I would like to kindly ask you to keep any further communication there.

    Regards,
    Boris Penev
    Telerik
     
    Check out Telerik Analytics, the service which allows developers to discover app usage patterns, analyze user data, log exceptions, solve problems and profile application performance at run time. Watch the videos and start improving your app based on facts, not hunches.
     
Back to Top