Closed marwie closed 1 year ago
Great catch, @marwie, and I believe that we should follow the approach in MaterialXView and display a warning dialog when this exception is caught in the Graph Editor, so that invalid input data never triggers a crash.
@marwie I'm testing this in a local build of the main branch, and it looks like this issue is now resolved, where the user can select and dive into the nodes of your example material without a crash. Let us know how this works for you in your local builds.
Hello,
I'm currently working on generating MaterialX graphs and naturally produce some invalid results.
When selecting some of those falsely produced nodes the editor crashes. Below is an example graph that produces a crash
Expected: Invalid graph nodes are marked in the graph and can be selected without crashing the editor Actual: When selecting invalid / not found graph nodes the editor crashes