Problem with initialization (Init order / Prerender / race condition?) about blazor.diagrams HOT 2 OPEN

Hello,

How are you doing things now?

from blazor.diagrams.

Hey, I worked around the problem with a bit of a dirty hack:

• I wrote a Component around the DiagramCanvas, called GraphViewer
• In the target component / page where I want to show a graph, I register the GraphViewer into a local variable using @ref=@...
• Inside the GraphViewer, I set the BlazorDiagram that is fed into the DiagramCanvas in OnInitializedAsync().
• Also inside the GraphViewer, I set a public readable prop "FirstRendered" to true in OnAfterRender() if firstRender is true.
• I then, in the target component, IF not PreRendering, wait asynchronously for the @ref-Variable of the GraphViewer to be set
• Then I register my custom Nodetypes etc.
• I then wait asynchronously again for the GraphViewer's FirstRendered-Prop to be true
• Only Then I call ApplyLayout() and ZoomToFit()

Additionally, using CSS, I make the canvas invisible until its FirstRendered Prop is true, and then with a transition I make it visible. This hides the un-arranged nodes that tend to "jump" to their final positions.

All of this does work, but it feels very hacky...

from blazor.diagrams.