You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"We want to do all our initializations in onIModelAppInit, but it seems the event is called very early before the ui/presentation initialization. Some of our initialization that depends on presentation being initialized fails in this callback.
Is it possible to introduce a third event or to change the location of onIModelAppInit firing position to end of BaseInitializer.initialize (here)? Or maybe you can notify using a new ‘onImodelJsInitialized’ prop which gets set when initialization is finished (like here)."
The text was updated successfully, but these errors were encountered:
Weigh pros/cons of moving onIModelAppInit to after total initialization. Failing that, add another callback when all deps are initialized.
From @ali Aslam
"We want to do all our initializations in onIModelAppInit, but it seems the event is called very early before the ui/presentation initialization. Some of our initialization that depends on presentation being initialized fails in this callback.
Is it possible to introduce a third event or to change the location of onIModelAppInit firing position to end of BaseInitializer.initialize (here)? Or maybe you can notify using a new ‘onImodelJsInitialized’ prop which gets set when initialization is finished (like here)."
The text was updated successfully, but these errors were encountered: