Brian Roth
Top achievements
Rank 1
Rank 1
Brian Roth
asked on 01 Apr 2013, 04:32 PM
Hello,
I'm having a problem with an editor template that I have inside the grid. I'm using an inline edit grid with keyboard navigation turned on. The editor template has 3 Kendo Numeric Textboxes in it, so when the user goes into the grid cell they will see all three textboxes. They are supposed to be able to type in those three inputs and then move on to the next cell to be edited. I've run into a couple of problems with this and was hoping to get some help as to the best way to handle this type of input.
1) My first issue was that the tabbed navigation did not work inside the cell. Initially focus goes to the first input control, which is as desired. But then if the user hits the tab key the focus goes to the next cell in the grid. The behavior I was hoping for was that focus would go to the next control in the cell. I was able to solve this issue by binding to the "keydown" event on the input controls and manually handling the tab key press and setting focus to the next control. But I'm wondering if there is a better way to handle this or if this is something that the control should handle out of the box?
2) The second issue is a little more problematic because I haven't been able to figure out a workaround. I'm using the grid Save event to run some custom logic to handle saving these multiple values back to my model. With the keydown code that I implemented above, the Save event fires after tabbing out of the first two textboxes. But when tabbing out of the last textbox the Save event does not fire. The difference with the last textbox is that I'm not overriding the keydown code anymore and just letting the grid navigate to the next cell. But shouldn't the Save event still fire in this case?
Let me know if my description makes sense or if I can provide any additional detail. If it would be helpful I can try to use the demo source code to create an example of my situation.
Thanks for your help!
Regards,
Brian
I'm having a problem with an editor template that I have inside the grid. I'm using an inline edit grid with keyboard navigation turned on. The editor template has 3 Kendo Numeric Textboxes in it, so when the user goes into the grid cell they will see all three textboxes. They are supposed to be able to type in those three inputs and then move on to the next cell to be edited. I've run into a couple of problems with this and was hoping to get some help as to the best way to handle this type of input.
1) My first issue was that the tabbed navigation did not work inside the cell. Initially focus goes to the first input control, which is as desired. But then if the user hits the tab key the focus goes to the next cell in the grid. The behavior I was hoping for was that focus would go to the next control in the cell. I was able to solve this issue by binding to the "keydown" event on the input controls and manually handling the tab key press and setting focus to the next control. But I'm wondering if there is a better way to handle this or if this is something that the control should handle out of the box?
2) The second issue is a little more problematic because I haven't been able to figure out a workaround. I'm using the grid Save event to run some custom logic to handle saving these multiple values back to my model. With the keydown code that I implemented above, the Save event fires after tabbing out of the first two textboxes. But when tabbing out of the last textbox the Save event does not fire. The difference with the last textbox is that I'm not overriding the keydown code anymore and just letting the grid navigate to the next cell. But shouldn't the Save event still fire in this case?
Let me know if my description makes sense or if I can provide any additional detail. If it would be helpful I can try to use the demo source code to create an example of my situation.
Thanks for your help!
Regards,
Brian
1 Answer, 1 is accepted
0
Accepted
Brian Roth
Top achievements
Rank 1
Rank 1
answered on 02 Apr 2013, 08:09 PM
Ignore this thread. I was able to reproduce the navigation behavior in a simpler situation and will make a new thread for that issue.