In this test the timings are actually off.
The initial search plugin runs on table open - where my expand is empty, but my rows().nodes() expand runs after that.
The search plug-in in this example will run on every table draw, including the table start up. Then the code for the row expansion is executed after the start up, so yes, that order would be expected.
Answers
In this test the timings are actually off.
The initial search plugin runs on table open - where my expand is empty, but my rows().nodes() expand runs after that.
Build your expand variable inside
initComplete
so its ready to use for the plugin. Same as you posted previously.Kevin
The search plug-in in this example will run on every table draw, including the table start up. Then the code for the row expansion is executed after the start up, so yes, that order would be expected.
Allan