Hello strk, Thursday, March 1, 2007, 2:24:16 PM, you wrote: s> This was the reason to provide a 'visitor' model for SnappingRanges2d, hiding s> the underlying container type. This use uses a random access iterator when s> it doesn't even need to. For a source-level compatibility with future container s> switch we could expose the iterator interface, or provide the visitor pattern.
Ok. But I ask you to do this as you are probably more experienced with it. s> Yest another possibility (the cleanset) would be to do everything inside SnappingTRanges, s> as I see _clipbounds are basically a SnappingRange2d now (right?) Not exactly. SnappingRange2d's use is to provide a common interface to maybe different snapping algorithms. _clippingbounds however is just a list of ranges which are ready to use. I would not mix the two. _clipbounds uses pixel coordinates, btw, not TWIPS as in SnappingRanges. Udo _______________________________________________ Gnash-commit mailing list [email protected] http://lists.gnu.org/mailman/listinfo/gnash-commit
