I am building a perspective view in a 8.0.9 project that contains an assortment of embedded views housed within flex containers. All of the other views in this project follow the same pattern. The containers themselves reside within a flex view.
On one of my screens it has an erratic loading behavior where all the containers scale up and down before stabilizing and rendering the data contained within the embedded views. I don’t experience this behavior on loading any other screens and have narrowed the cause down to a single embedded view that is high complexity and contains several flex repeaters for various icon sets and data labels.
So far I have tried setting the loading mode to blocking on the screen view and every sub layer of embedded views so that nothing on the screen itself at any embedded view level has a loading mode of non-blocking. This has not affected the screen startup behavior.
Is there anything I can do to mitigate this or have I reached an upper limit for screen complexity at which scaling occurs in a reasonable time frame without making the screen appear glitchy on startup? Am I approaching my screen construction inefficiently by unitizing everything into embedded views? Will I get an appreciable performance gain if I put everything inside of the view itself?