Updating a design while iterating(C#)

Hello all,

I have a component that plays with a geometry made of lines. at the moment when the iteration are done the component draws the final geometry to rhino viewport. is it possible to show the updated design after each iteration in the viewport? without breaking the loop of course.

thanks in advance

Roey

Attachments:

GridSolver.cs, 30 KB

Replies to This Discussion

Permalink Reply by peter fotiadis on September 6, 2015 at 2:22am

Hmm ... it's the right time for the Paris Hilton (results always in Pink) collection of demos.

See attached.

BTW: I'll modify yours soon.

Permalink Reply by Roey Yaniv on September 6, 2015 at 2:26am

nothing attached...

Permalink Reply by peter fotiadis on September 6, 2015 at 2:28am

Indeed ... for some reason it's impossible to attach anything.

I'll try later

Permalink Reply by peter fotiadis on September 6, 2015 at 2:29am

2nd time lucky? (this IS nerve breaking to the max, wonder what's happening)

Attachments:

Paris_Hilton_VS_GH_V1.gh, 139 KB

Permalink Reply by peter fotiadis on September 6, 2015 at 2:31am

Also get this ("abstract") stuff

Attachments:

DelayControlV12A4.gh, 119 KB

Permalink Reply by Roey Yaniv on September 6, 2015 at 2:46am

i don't understand how does this answer my question

Permalink Reply by Giulio Piacentino on September 7, 2015 at 4:09am

Hi Roey

I will try to answer your question in general terms, so that you can get further with the code on your own.

If you are willing to stay as much as possible within Grasshopper SDK conventions, you will have to save the state of the loop at a certain point and do the next moves independently in a new iteration.

Ideally, this would suffice:

- add a number of fields that store the state of the loop
- add a counter field that starts at 0

When the component is called the first time (counter == 0), then fill the fields with data coming from the inputs.

- add a reset toggle (Boolean) to reset the counter to 0.
- use the stored data from the fields each time you update the solution.

You could also do a number of sub-iterations per update.

Alternatively (option 2), you could try to request a view redraw from within the component SolveInstance(). This will create an even tighter coupling between viewport redraw and solution, and might work less efficiently as you are requesting to redraw the screen while computing your solution, but I'd like to mention it as a "cheaper" alternative.

I hope this helps,

Giulio
--
Giulio Piacentino
for Robert McNeel & Associates
giulio@mcneel.com

Attachments: