Hmm, where to begin.
With IronPython3 being in active development and Unity and other applications beginning to support IronPython I don’t know what will drive me to learn any statically typed language.
Be it as it may, I don’t want stuff drawn on my screen inside Rhino viewports that is an unnecessary clutter while I have curves and points in wireframe mode. At least not with the current use case in mind. Conduit seems a nifty way to create video game like gui. (perhaps Blender Game Engine embedding could be a nice addition to Rhino as well )
This will use the Rhino sole process for the calculation and just like Grasshopper lags that will lag as well. I want the calculations done in another process. Whether I’m going to use subprocess or some other method… That is something I need to clear out since I don’t know anything there and good IronPython examples are a rarity in internet. Just look at Clement’s example
Try moving the point. Before you release it the conduit text doesn’t update. This is because sticky is not updating in real-time.
I want exactly that. I want the value displayed in that separate process window to be displayed in real-time and not to start recalculation after I release the point.
I want an update of this conduit to be implemented the same as in Grasshopper canvas. But only when moving components around and connecting/disconnecting wires. As soon as Grasshopper starts taking Rhino objects it can no longer display values in real-time.
UPDATE: Just proving a point.