Hi Rob,
> Currently is it right that not all sweep opperations update
> automatically?
One of the limitations currently is that if your operation produces multiple separate output objects from one input object, that history updates won't work in that situation.
When you have a segmented path with sharp corners in it (like a polyline), then it will produce multiple separate output objects for each segment with the current sweeper.
> Will this sort of behaviour be fixed when you come to look at
> auto mitering of sweep shapes?
Yeah actually I think it should because the mitered result will be one solid (which will count as one output object even though it is made up of multiple joined surfaces) so it should then work with history updates in the current system.
- Michael
|
