Could it be that you're not closing your path? Right at the end you might need:
CGContextClosePath(context);
No one in particular
2010-09-14 22:14:32
A:
I actually missed one line while copy pasting. But i have CGContextSetStrokePath(context) right after the last line of code within the function.Does CGContextSetStrokePath close the path as well? Or does that have be added as well?
Swapan Rajdev
2010-09-14 22:25:56
Where did you get CGContextSetStrokePath() from? I can't find that in the developer documentation.
No one in particular
2010-09-14 22:42:36
Sorry that was a typo: CGContextStrokePath() is what i have.
Swapan Rajdev
2010-09-14 22:45:09
A:
Have you profiled your app to figure out where most of the time is spent when it slows down?
It could be in the path stroke in core graphics, in your computational methods, or somewhere else. If you start optimizing before you have any profile/performance data, you may end up spending time in the wrong place.
hotpaw2
2010-09-14 22:43:10
Thanks for the suggestion. I have not profiled my app. Is instruments the best tool to gather such data?
Swapan Rajdev
2010-09-14 23:01:47