Am 12.03.2010 um 03:13 schrieb Mazen M. Abdel-Rahman:
For the calendar grid I was creating an NSTrackingArea for each cell - in my
case (the calendar is for 7 days with 15 minutes per cell) there was 672
NSTrackingAreas.
I will have to look at alternative solutions to all these
On 10 Mar 2010, at 17:13, Mazen M. Abdel-Rahman wrote:
Hi All,
I was able to write a simple calendar view that uses basic cocoa graphics to
draw directly on the view (NSBezierPath, etc.). I actually use several
different paths for drawing the calendar (it's a weekly calendar) to allow
Hi,
are you drawing ALL of your paths whenever the user scrolls or only the ones
that are within the visible rect? If the first, you may try to change that to
the second and gain lots of performance. I draw a sound wave view and when
drawing all of it while zoomed into it, it is sooowww.
Thanks everyone for your help on this.
I started using an image cache - but that did not improve the performance as
much as I thought it should. I then removed the section of my code that
creates NSTrackingsAreas - and the improvement was immediately noticeable.
For the calendar grid I was
Hi Mazen, how are you?
Maybe I can offer a tip on how to improve your performance: there is a
technique called BSP-Tree which divides the space in two equal parts
recursively, creating a tree of subdivisions. This technique improves the
search of which area of the space (in your case, the
Hi All,
I was able to write a simple calendar view that uses basic cocoa graphics to
draw directly on the view (NSBezierPath, etc.). I actually use several
different paths for drawing the calendar (it's a weekly calendar) to allow
different horizontal line widths (hour, half hour, etc.). The
