This is a migrated thread and some comments may be shown as answers.

Rendermode and tab key problem

8 Answers 148 Views

PropertyGrid

This is a migrated thread and some comments may be shown as answers.

8 Answers, 1 is accepted

answered on 29 Oct 2013, 04:13 PM

750991-RadGridView-WPF-AR-1.zip

Hello Markus,

Please find attached a sample project that meets your requirements.

Regards,
Yoan
Telerik

TRY TELERIK'S NEWEST PRODUCT - EQATEC APPLICATION ANALYTICS for WPF.
Learn what features your users use (or don't use) in your application. Know your audience. Target it better. Develop wisely.
Sign up for Free application insights >>

answered on 17 Aug 2015, 07:31 AM

I have a request from our users to implement behavior in RadPropertyGrid that would allow them to edit next field just with one Tab key press similar to web forms experience they already know. I have downloaded sample from Yoan, but after trying it I think that when Markus said:

I want to edit each row with a single tab key press.

he actually wanted not just to jump to next field but also go straight to edit without the need to press F2.

I tried to implement custom PropertyGridCommandProvider and so far I've only managed to jump to the next field with single Tab, jump from the last to the first field and jump back with Shift+Tab from the first to the last field. But I can't find a way to go straight to edit mode without F2 key.

Is there a way to achieve this behavior? Because otherwise I would be forced to abandon RadPropertyGrid and create the entire form myself with properly set TabIndexes.

answered on 20 Aug 2015, 07:31 AM

Hi Vitalij,

Due to the great interest in the behavior that you illustrate, we introduced some a feature in our Q1 2015 version: Support for disabling built-in navigation and controlling processing of handled events. Two properties were introduced - PropertyGridCommandProvider.EnableBuiltInNavigation and PropertyGridCommandProvider.ShouldProcessHandledEvents.

Setting the PropertyGridCommandProvider.EnableBuiltInNavigation property to False should do the job you want. In this way you will have virtualized PropertyGrid and the navigation will be performed through the editors.

Please let me know if this works for you.

Regards,
Martin Vatev
Telerik

Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Feedback Portal and vote to affect the priority of the items

answered on 20 Aug 2015, 03:16 PM

Hey Martin, thanks I've totally missed that property. Double Tab press is needed for jump to another editor, thus it still does not feel as an optimal solution but I can live with that. But selected property is not following focus to different editors. In my opinion, selected property should be synchronized with actively focused editor.

Additionally, when I select some property with a mouse and then press Tab, focus is always moved to the first editor and not to the editor of selected property, which is probably a bug.

I think that there is a great inconsistency with keyboard navigation throughout the entire PropertyGrid control.

Finally, when browsing demos I’ve found that in “RadPropertyGrid DataTemplateSelectors support” single Tab press navigation between editors works in default render mode without any additional settings, so probably I’m going to leave Flat render mode and its advantages in order to achieve classic user navigation experience they already know from other applications and web browsers.

Regards, Vitalij