In the grid I have an event wired up to the editcellstarting event. Sometimes I cancel this event to prevent the editors from showing. But when a user is tabbing, it cancels the tab event so the grid doesn't naturally flow to the next record. How can I get around this?
LegendX = Show EditorsY = Prevent Editors
Row 1: X | X | X | X | XRow 2: X | X | Y | X | XRow 3: X | X | Y | Y | X
First row tabs perfectly!Second row tabs stop after the second column. User has to manually click on column 4 to start again.Third row tabs stop after the second column. User has to manually click on the column 5 to start again.
The tab should naturally shift to the next available column. After looking at the source, I saw that the code returns with a "Cancelled" response and the invoker does nothing with it except returns. I don't want to cancel it, I want to skip it. How can I achieve this?
Hello Karthik,
What I can suggest you based on your current scenario is after canceling the editCellStarting event to find the next cell which you want to be editable and to call startEdit API method for this cell. If you have any questions, please let me know.
Regards,
Tsanna
Dirty. We would need to maintain a list of currently visible columns and their indexes. The tricky part is to invoke "tab" on the next row if the rest of columns are non-editable. There aren't any internal api calls that will do this for us? :)
I'll find it! Yes I know we can't rely on it across updates and service updates.