Skip to content

Fix the "0 is not set" error message

This MR fixes the mysterious error message "0 is not set" that shows up when loading certain model files into modelbuilder. The problem is that the vtk session Import operator was not checking whether an optional string item named "filetype" was enabled or not. The error message showed up after a recent MR by chart3388 that added some error checking to ValueItemTemplate. This MR checks the "filetype" item thereby avoiding the error message.

Merge request reports