tags:

views:

103

answers:

2

Maybe this can solve out the ugly delay with touchesBegan: to touchesMoved:. It is caused artifically by iPhone OS to check if the user really wants to move. In some situations the finger must be tracked without delay, otherwise it just looks ugly. You see that everywhere through iPhone OS. Sliders, Scroll Views.

Maybe accelerating the system time makes the delay smaller.

+2  A: 

You can set UIScrollView:delaysContentTouches to be NO, which will solve this.

You really don't want to change the system time to hack out something like this. Do you want apps you're using to screw up your calendar and alarms and your phone log, etc?

groundhog
+1 on the verbose.
jms
You're right, that could screw up other things. I really think it sucks apple did not think much about the ugly appearance that can be caused by this kind of delays. A simple way to deactivate any waiting would have been fine. Unfortunately, setting delaysContentTouches to NO will still cause a small delay. It still waits to determine if you really want to scroll. That's stupid. I measured it in a blank new project. About 0.15 sec., which is just enough to let a tactile app look like it has programming errors.
HelloMoon
A: 

I asked a similar question, still open.

I don't think there's a way around it for now, seeing as even the ultra lickable "slide to unlock" slider suffers from the problem.

At this point I think the only solution is try smoothing this initial bump out with a bit of position interpolation.

Rhythmic Fistman