I need help with getting my client side objects into variables.
On the onload event of the html-body I call a delayed (1000ms) function that loads my different IG controls into a global variable. Either way I try to load the objects with ig_getWebControlById and $find it returns null except of the Warp, where I get an object. Even on a later event the functions don't return the correct object.
Could anyone please help me with this issue?
Most of our ASP.NET controls (other than the ASP.NET AJAX controls built atop of our Aikido framework) have their own "helper functions" used to get reference to the correct client-side object. The function ig_getWebControlById is used for WARP, but may not be used with other controls..
What other controls are you trying to get a reference to? You mention WebGrid in the tags of your post; the helper method to use for WebGrid is: igtbl_getGridById()
Thank you for your quick reply.
Yes, I also tried it with UltraWebGrid and also with WebToolBar, WebDialogWindow and WebSplitter. With the WebDialog $find worked pretty well. Now I will get the controls by their specific functions.
Due to the description in the CSOM documentation I thought ig_getWebControlById() would work with any Infragistics Control.
This is what is said in the documentation:
"function ig_getWebControlById(id)
"function
This works with all Infragistics NetAdvantage for ASP.NET controls. It takes in the ID of the control, and returns that control if a control with that id is found."
I've found the spot in the documentation you've mentioned. I'm not certain that this is correct. I'm following up with our developers to confirm.
I've confirmed that this documentation is indeed incorrect.
The function ig_getWebControlById() is meant to work for a subset of our ASP.NET controls, not for all of them. Among these include WebAsyncRefreshPanel, WebScheduleInfo, WebDayView, WebWeekView, WebMonthView, and WebCalendarView. I don't know at the moment if this is a complete list, as there may be a couple of other controls this might work for.
I'm passing this information to our documentation team, so that the docs can be updated accordingly.