Hello,
We are using the XamDockManager to display screens, and we are running into an issue with initial loading/rendering of the panes. For example, we have some content that takes a few seconds to load/render, and when we display this content in a floating pane using the XamDockManager the floating window initially becomes visible displaying no content (because the content is still rendering). After a few moments the content loads and becomes visible. This initial blank screen doesn't look good, we would like the window to not appear until the content has loaded.
Why does the floating window become visible before the content is rendered? In the XamDockManager code is the window being displayed before the content is assigned? We are currently using version 2013.1.
Any help would be appreciated.
-Chris
Actually, I don't think this is caused by Infragistics, I think it is being caused by how we are generating screen content. I can't reproduce with a simple example.
Hello Chris,
Thank you for your post!
I have been investigating this issue that you are seeing, and I believe this behavior that you are seeing is expected. The rendering of the ContentPanes in the XamDockManager is not dependent on the content that is within it. That is to say that if a ContentPane is added to the XamDockManager.Panes collection, it will render regardless of whether or not the content within it has been rendered yet.
To get around this, I would recommend that you have the ContentPane to be floated have a MaxHeight of 0 so that it isn't visible at the start, but the elements inside of it still render. If you hook into the Loaded event of these elements that you have inside of your ContentPane, you can then change the height of the content pane be visible, as this event should fire once your elements are done Loading. The reason I recommend the MaxHeight property rather than the Visibility property is because if you set the ContentPane's Visibility to Visibility.Collapsed, the elements inside will not render.
I hope this helps you. Please let me know if you have any other questions or concerns on this matter.
Sincerely,AndrewAssociate DeveloperInfragistics Inc.www.infragistics.com/support
Thanks Andrew. Just to follow up on this, I found that this issue only occurs if we set an initial floating window size. If we don't set an initial floating window size, the window does not appear until the screen content has finished rendering.