Than you for your hints!
Regrding the the sleep() command it was only due to prototyping and I wanted to have a chance to see if the sliders stepped up properly…
What I plan to do is to bake some geometry at each step of the Slider + capture for video animation etc, which seems risky to do with a timer (like, how do I know it’s done baking before next tick?).
I would also use the stepped values from the for loops for stepwise update of parametric creation of geometry to be baked, and these parametric values would in turn be affected by at least two other sliders/for-loops combined. I will nest at least three for-loops (with sliders) to update the geometry and bake it at each step.
I based my proto-code on the following video (Scripted from RhinoPython, not from GhPython) where the stepping of sliders didn’t need timers. Wouldn’t a timer only be at risk of being out of sync with the baking(?) :
http://designalyze.com/automate-grasshopper-python/automating-grasshopper-part-2 (and 3)
I also use instance guids to identify the sliders :
gh = Rhino.RhinoApp.GetPlugInObject("Grasshopper")
slider_y_abd = "9ec5e15c-b939-4643-b90c-7aaf84a38813"
for abd in range(0, 10, 1):