Yeah another class would be one solution.As an aside, I think in some cases it should be acceptable to break code. I sometimes find 'it breaks code' to be an unfortunate discussion stopper. With point releases and change logs, I think breaking code is less of an issue than it used to be, as users can be clearly warned in advance of upgrading.
I don't think SCCompositeView has been extensively used directly, and those who have used it have often mused on list about this odd behaviour.
We could also add a new SCRelativeCoordCompositeView ;-) class and consider deprecating SCCompositeView.
Another solution would be to provide compatibility methods, so that people could get the old behaviour with minimal changes, at least for a transition period.
S. On 6 Dec 2007, at 23:43, James Harkins wrote:
On Dec 6, 2007 6:34 PM, Scott Wilson <i@xxxxxxxxxxxxxx> wrote:I've never understood why SCCompositeView doesn't. I'd be happy to see it changed.How should we handle backward compatibility for people who depend on the old behavior? I totally agree that the current behavior is dodgy, but a change like this will break code. Maybe composite view should change and there should be a SCAbsoluteCoordCompositeView? :-p hjh -- James Harkins /// dewdrop world jamshark70@xxxxxxxxxxxxxxxxx http://www.dewdrop-world.net "Come said the Muse, Sing me a song no poet has yet chanted, Sing me the universal." -- Whitman _______________________________________________ Sc-devel mailing list Sc-devel@xxxxxxxxxxxxxxx http://www.create.ucsb.edu/mailman/listinfo/sc-devel