Hi,

I am also facing the same issue in xamgrid. Please let me know if you find any work around.

Thanks,

Hemant

Hello,

I have sent your Product Idea (Skip RaedOnly Cells) directly to our product management team.  Our product team chooses new Product Ideas for development based on popular feedback from our customer base.  Infragistics continues to monitor application development for all of our products, so as trends appear in requested ideas, we can plan accordingly.

We value your input, and our philosophy is to enhance our toolset based on customer feedback.  If your idea is chosen for development, you will be notified at that time.  Your reference number for this Product Idea is PI13030127

If you would like to follow up on your Product Idea at a later point, you may contact Developer Support management via email.  Please include the reference number of your Product Idea in the subject and body of your email message.  You can reach Developer Support management through the following email address:  dsmanager@infragistics.com

Yes, please go ahead and add this point to your product idea list. Because otherwise, every developer who is consuming this control will have to write this functionality on her own, which I am thinking is common. Additionally, we can have a boolean property say AllowTabNavigationOnReadOnlyCells which would decide that read only cells would be part of tab navigation or not.

Also, if we add a pager to the XamGrid (Using PagerSettings), the tab focus always go to Pager first and then the cells, irrespective of whether it is kept at the top or bottom. TabNavigation should also consider position of the pager control.

Thanks for your efforts and help on this.

Hello,

Currently this approach seems to be the best one for achieving the result you want. If you want I can log a product idea, so this could become built in functionality.

Looking forward for your reply.

Thank you for your reply Stefan.

I had a look into the solution provided by you. It works fine with theexample provided by you. But it seems to be very specific to the model binded to the grid.

The inherited control which I am using in my application is used in almost 70 pages and forms. So I need to fix this in the control itself in a generic way. So I can not check against the Key property of the ActiveItem.

But if you are saying that this is the only possible way to achieve the fix to the problem mentioned, I think I will have to look into the cell properties like -> IsReadOnly/IsInAddModel/IsEditable and also check if there is any EditRowSettings/AddRowSettings available for the grid.

Apart from that, I will also have to handle Shift Tab. So following are the points to be taken care of:

1. On tab -> navigate till we reach next editable/focusable cell.
2. If it is last such cell of the row, shift focus to first such cell in next row.
3. If it is last such cell of the last row, shift focus to pager control’s first focusable control.
4. Shift + tab -> navigate till we reach previous editable/focusable cell.
5. If it is first such cell of the row, shift focus to last such cell in previous row.
6. If it is first such cell of the header row i.e. header checkbox, shift focus outside of the Grid.

Please correct me if I am wrong. Seems like a lot of handling and that too in the KeyDown override :(

I wish this was handled already in the XamGrid.

Hello Hemant,

I am just checking the progress of this issue and was wondering if you managed to achieve your goal or if you need any further assistance on the matter.