> Indeed. DrGeo is not multithread safe. > > In this example, the animation is done in a background thread, at the > end of the smalltalk code this is the "canvas do: [] loop" code. > > So when playing interactively with the sketch, changing parameters for > example, your are forcing a sketch update, and at this exact same time > the animation tread may be in the re-rendering phase. So the artefact > you see is because the sampling of the locus is recalculated in one > thread and rendered (incomplete) in another thread. > > We are exploring here the Dr. Geo bounds... > I am not sure I want to investigate the case yet.
don't :) Wait for a real use case Stef
