out of the blue a few things occurred to me
I suspect (but don't know!) that all geometry is "rendered"
independently with CGAL and then (assuming the loop is in some other
operation ie hull or difference) those separate geometries are sent to
CGAL together once the loop has finished.
Do to the nature of the language trying to fix all values just before
run time (as it were - almost like verilog!) each iteration of a loop
basically independent from another.
Off hand I can't think of any way you could effect a different iteration
of a loop from within the loop.
Assuming my assumptions are correct! does it not follow that each
iteration of a loop could be evaluated in any order.
In that case could you not have a pool of slots (number chosen in
settings) and assign a thread to each slot as each thread finishes it
iteration of the loop (which it wouldn't even know was a loop) that slot
put the geometry in the "world" and then creates another thread for the
next un-rendered iteration.
Okay I probably could have worded that better and do appreciate I know
next to nothing about the code base, but does this idea even sound
plausible ?
out of the blue a few things occurred to me
I suspect (but don't know!) that all geometry is "rendered"
independently with CGAL and then (assuming the loop is in some other
operation ie hull or difference) those separate geometries are sent to
CGAL together once the loop has finished.
Do to the nature of the language trying to fix all values just before
run time (as it were - almost like verilog!) each iteration of a loop
basically independent from another.
Off hand I can't think of any way you could effect a different iteration
of a loop from within the loop.
Assuming my assumptions are correct! does it not follow that each
iteration of a loop could be evaluated in any order.
In that case could you not have a pool of slots (number chosen in
settings) and assign a thread to each slot as each thread finishes it
iteration of the loop (which it wouldn't even know was a loop) that slot
put the geometry in the "world" and then creates another thread for the
next un-rendered iteration.
Okay I probably could have worded that better and do appreciate I know
next to nothing about the code base, but does this idea even sound
plausible ?
