5 ms·
It's more computationally expensive to calculate, draw and attach tap events to rows in a UITableView if you're trying to still keep 60fps scrolling. It's hard
by flyosity 15y ago
It's more computationally expensive to calculate, draw and attach tap events to rows in a UITableView if you're trying to still keep 60fps scrolling. It's hard enough to get glass-like scrolling with dynamically-loading avatars and random strings of text at different font sizes all over, but tappable things and highlighting makes it even harder.
- ry0ohki 15y agoEchofon does it somehow? I'd rather have form over function, but I'm probably in the minority.
- BigZaphod 15y agoTwitterrific has done this for a long time. It was hard to make it perform well, but not impossible.
- Hrothgar15 15y agoStill not 60 FPS. :)
- Zev 15y agoUm. What? While, yes, it is more expensive to detect that something is a link than not, it isn't that expensive to do. Neither is drawing an attributed string with Core Text. Yes, its hard. No, it isn't nearly as hard as you're making it out to be. And making things tappable/highlightable? The tableview isn't scrolling when you're tapping. Detecting a tap and performing some calculations to determine which text run the tap falls on cannot cause scrolling performance to go down.