I found this when trying to change to the new Prometheus controls in my web app. I have a page with a multiview and several views with databound controls. Which view I display is dependent upon the current app state.
The typical ASP.NET behavior is that a given control does not bind until it's view is displayed on the page. This is how the previous RadAJAX version worked as well. The Prometheus version is causing all controls in all views to databind upon the first page load.
To reproduce this:
Create a page with a multiview and two views. In each view add a control and bind it to a datasource control. Set the 1st view as the default so it displays when the app loads. Set up an event handler for the 2nd view datasource's "selecting" event. You will notice that it does not fire when the 1st view is displayed. Now, wrap the multiview in a Prometheus AJAX control and rerun the application. You will see that the "selecting" event of view 2 is fired even though the view has not been changed.
I hope this makes sense. Am I overlooking something?
Thanks!
John
Pyron Technologies
The typical ASP.NET behavior is that a given control does not bind until it's view is displayed on the page. This is how the previous RadAJAX version worked as well. The Prometheus version is causing all controls in all views to databind upon the first page load.
To reproduce this:
Create a page with a multiview and two views. In each view add a control and bind it to a datasource control. Set the 1st view as the default so it displays when the app loads. Set up an event handler for the 2nd view datasource's "selecting" event. You will notice that it does not fire when the 1st view is displayed. Now, wrap the multiview in a Prometheus AJAX control and rerun the application. You will see that the "selecting" event of view 2 is fired even though the view has not been changed.
I hope this makes sense. Am I overlooking something?
Thanks!
John
Pyron Technologies