![]()
Any chance that this fix solves or brings us any closer to the solution for the lack of control over plugin load order in general?
reference:
What dictates the load order for Grasshopper Plugins? - #28 by s_oosterhof
It has caused quite a bit of headaches here. In my team we have some internal (standard C# SDK) plugins that depend on each other and having to deal with them loading and initializing out of order adds uneccessary level of complexity.