jQWidgets Forums
Forum Replies Created
-
Author
-
March 2, 2021 at 4:10 pm in reply to: "TypeError: this.rowinfo is undefined" after ready callback "TypeError: this.rowinfo is undefined" after ready callback #114768
Peter,
I have used $(document).ready to both set up my treeGrid and subsequently call expandAll and selectRow.
I have found that if I set async to false in my treeGrid’s dataAdapter and remove the 3 second delay before expanding and selecting, this too will cause it to work properly. But it seems to be either/or. I can not rely on the ready callback if it is asynchronous, causing me to need the delay mechanism. Choosing synchronous, well then it works.
It just seems the ready callback is not actually ready if the dataAdapter is an asynchronous AJAX call.
Thanks
March 23, 2020 at 6:49 pm in reply to: jqxTreeGrid rowSelect: grabbing row is different whether the base or a child jqxTreeGrid rowSelect: grabbing row is different whether the base or a child #111512I think I’ve found the issue. My “dataFields” definition was lacking the specification for several columns. This event.args.row for the base of the parent/child hierarchy reflected this by not containing the missing columns as would be expected. However, the branches of the parent/child hierarchy read and included all the JSON regardless of my “dataFields” definition, and therefore those event.args.row did include the missing columns. As I clicked around the grid, most rows were children and provided the column as I expected, but the root would not, hence my confusion.
So, my bug was to forget to include all the columns that I needed in the “dataFields”, however I believe the subsequent child rows should also use the “dataFields” and reflect the error rather than reading everything regardless.
Thanks again for helping me move forward.
March 23, 2020 at 3:26 pm in reply to: jqxTreeGrid rowSelect: grabbing row is different whether the base or a child jqxTreeGrid rowSelect: grabbing row is different whether the base or a child #111500I’m not sure what I was doing wrong, but working through your example helped me to debug my code so that event.args.row is working throughout.
Thank you.
February 28, 2020 at 3:32 pm in reply to: Using cache:false is ignored causing _=1582749028718 to be appended to URL. Using cache:false is ignored causing _=1582749028718 to be appended to URL. #108263No change. The “_=1582903579291” is still appended to the URL.
Is the cache:true|false in the correct place? I could not find where it should be located in the API documentation.
-
AuthorPosts