There seems to be more and more differenced between the old splitter and the new one which is really causing some serious snags.
For example, if you had this in the root of the application:
/Master.master (with a two-pane splitter, one contains a ContentPlaceHolder,a nd the other has a ContentUrl of "Home.aspx")
/Default.aspx (using the master page)
And then also had this:
/SubFolder/Default.aspx (using the master page)
The old splitter would load the Home.aspx file relative to the location of the Default.aspx, so when you moved from one folder to another, so too did the "Home.aspx" file.
The new splitter always loads the "Home.aspx" file located in the root directory. Which brings me to the Client-Side Events problems I'm having.
Since with the new splitter I now have to tell it what page to load in the external content pane when I change folders, I'm adding a response script to the master page's RadAjaxManager on the page load to load the desired page. The response script is simply "LoadContent('Home.aspx');", which calls the following function located on the master page:
|function LoadContent(url) |
| var splitter = $find("<%= RadSplitter1.ClientID %>"); |
| var pane = splitter.GetPaneById("RadPaneContent"); |
| if (!pane) return; |
| pane.SetContentUrl(url); |
This worked great with the old splitter, but with the new one, it finds the splitter ok, but GetPaneById fails with "object does not support this property or method". If I do splitter.get_Height() it works fine so I know that it is indeed finding the splitter object.
The documentation and the online examples both say that GetPaneById should work, which is really really frustrating.
Any help out there is sincerely appreciated.