when trying to use the existing flexigrid events you have foreseen, I stumbled upon the inability to reference the flexigrid object from my own callback functions. The reason is you call events in the context of parameter object, like:
Code:
if (p.onRpChange) p.onRpChange(+this.value);
So in my callback functions this will refer to p, but how I can reach for the grid itself? Wouldn't it rather make sense to call event callbacks the following way?
Code:
if (p.onRpChange) p.onRpChange.call(t,+this.value);
Thus setting the flexigrid object as a context. What do you think? Any objections/pitfalls?
The other question is the approach of calling user event callbacks: in addition to default (built-in) events, or replacing them. Currently, in some cases, you go the latter way; therefore, if I need to add my own functionality, while keeping the default behaviour intact, I must copy your code in my own callbacks and reuse it. Not necessarily the best idea perhaps... Well, I guess this require separate discussion and possible rethinking of the flexigrid event system... Maybe next time [/quote]
Hi snobo,
Yes the original idea with the callbacks was to create your own, rather than extend, thats why there is no way of going back to grid itself. I mainly added this API to allow people apprehensive about using Ajax on their development, so onRPChange, onChangeSort, and onChangePage, was supposed to allow them to modify the URL or make another post, then just re-render the page.
Anyway, you can still reference the flexigrid, just by calling it with flexOptions method.
[/quote]