I am hunting down what is causing the display of this error message, but there really is no clue as to what causes this, except that, unless I check “Do not show this message again”, it keeps popping up.
Also, after discarding the message, the definition essentially freezes.
This could be related to the “fix” for the recent crashes, because that definition didn’t freeze like that ; it just worked until it crashed Rhino.
If this is caused by something bad in my definition, my only investigation method is to :
-Lock the canvas
-Open the definition
-Disable a part of my definition
-See if the error message pops up
-If it does, start again and disable more components until the origin of the problem can be singled out
This method has worked for me in the past, but I really wish the “Breakpoint call stack” (whatever that is) gave me simple information about what causes the issue.