-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
1 changed file
with
1 addition
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
108d04e
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fine!
Another thing about which I think last time. What do you think about extending parameters of
dataInit
with additional parameters likerowid
or some more (column name for example). CurrentlydataInit
be called frombindEv
. The$.jgrid.bindEv
will be called from two searching modules (toolbar and filter) and from tree editing modes. You extended parameters of callbacks of form editing with additional parameterfrmoper
which can be"add"
or"edit"
. I find the changes very good because one need sometime do different things for adding and editing. In the same way one need sometime do different things indataInit
callback depend on the context of usage.For example one can initialize
datepicker
with different options in searching toolbar, inline or cell editing (where we have restricted place) and Searching Dialog and editing form. One can useshowOn: "button"
option in form editing and searching dialog and don't use it in other cases.In the same way it could be practical to call
autocomplete
inside ofdataInit
withsource
having additional parameterrowid
or with other parameter from the current line (one can get the information ifrowid
is known).What do you think about such extension of
dataInit
?Best regards
Oleg