Ah, I was afraid of that. Really, I have to say, it's not much of an API
design when there are two ways of doing things and they silently break and
cancel each other out like this. We'll consider our options but as suspected
it'll probably not be possible to support both then.
Thanks Nic!
/ V
As far as I know, you dont.
X.iOS has alway followed the following model:
1. you make a new object (UIScrollView on your case). It makes its own
UIScrollViewDelegate in the background, which calls the .Scrolled
events (and all the others)
2. you assign the delegate. This clears (or rather,
