A lot of people in my company hate the "click to activate edit mode". For the boolean editor, you have to click to edit it and then click again to switch it.
Replacing the rendering with just a checkbox has weird results. So I've tried to come up with a custom editor:
Is this the right way to do it and maintain that changes get fired on the datasource change event? Am I messing up data binding?
Is there any more information about custom editors except for the one example here? (http://docs.kendoui.com/api/web/grid) It's very terse info!
That api page mentions these items, but there is no example use that gives any indication what kind of options are "additional options" ??
Replacing the rendering with just a checkbox has weird results. So I've tried to come up with a custom editor:
function instantBoolEditor(container, options) {
// flip value
options.model.set('enabled', !options.model.enabled);
// replace html with the same template the column uses
[...]
// should I do something like trigger change?
options.model.trigger("change", {container: container, model:options.model});
}
Is this the right way to do it and maintain that changes get fired on the datasource change event? Am I messing up data binding?
Is there any more information about custom editors except for the one example here? (http://docs.kendoui.com/api/web/grid) It's very terse info!
That api page mentions these items, but there is no example use that gives any indication what kind of options are "additional options" ??
columns.editor.container Object
The container in which the editor must be added.
columns.editor.options Object
Additional options.
columns.editor.options.field String
The field for the editor.