Alternatively you can write your code in a class which runs outside of the solution (like Galapagos). This can mean putting it inside a window and have it triggered by button presses or other UI events, or it can mean creating a class instance which gets ‘activated’ once a solution is finished.
I have previously successfully used ScheduleSolution() to handle websocket messages containing a single set of slider values. I used the method you provided here I have also looked at Colibri, but I specifically need to apply sets of slider values at a time. This is to save you time, I’ve done my research.
I am trying to get Grasshopper iterate through a list of “sets” of slider values from within my component. I am basically getting grasshopper to batch execute sets of generated slider values that will be read by my plugin when loaded in a grasshopper definition. What is the best way to do this using ScheduleSolution() ? I would like it to start executing the moment the definition loads, and not from a UI event. Can you please provide a code sample for the Class instantiation method you described ?
PS- In Rhino6, I am able to change slider values, but the Geometry dependent on these sliders is not recomputing (right now it’s just a cube). The C# script you provided doesn’t work either.
To recap -
This is the code you provided in 2017 but doesn’t work for Rhino6 as is. I use the same logic in my component.
This is my modification
and partially works, but behaves unpredictably. The number of times it loops over the sliders is out of control.
Please let me know if you have a solution.