sorry, CATiledLayer actually improves performance. the downside is, the tiles need time to be drawn and are faded in using an animation of 0.25 seconds. so, if there are 6 tiles to be drawn you end up seeing iOS building the "mosaic" in a total of 1.5 seconds.
i took some looks at the scroll view suite already. will do it again until i get the point that makes the difference. thank you very much for your time - you actually helped my brain taking another route ;) - m 2010/6/24 Matt Neuburg <m...@tidbits.com>: > On or about 6/24/10 2:50 AM, thus spake "Martin Glaß" > <glas...@googlemail.com>: > >> additionally, if the user scrolls through the pages very fast, no >> content is visible until all CATiledLayers of a page's content gets >> drawn calling the above method. >> I am using CATiledLayers to improve performance during drawing and >> zooming (each page can be zoomed, additionally). > > Hi, Martin: > > I am not an expert with CATiledLayers so I do not know what complications > are introduced by their use in this context. But it seems to me that you are > saying two opposite things: on the one hand, CATiledLayers are supposed to > improve performance, but on the other hand, you say they are ruining > performance. :) > > Perhaps the trouble is not the CATiledLayers themselves but the technique by > which you are supplying what it is that the CATiledLayers are to draw. You > could, of course, figure that out with Instruments. > >> i think about adding/removing subviews like you do in your app - but >> what about performance if the user scrolls fast? > > Well, rule number one of programming is Don't Optimize Prematurely. Until > you try it and measure performance with Instruments you do not know whether > this will really be a problem. Perhaps having fewer subviews would make > everything faster! You have to try it to find out. > > In my own application, where I add and remove subviews every time the user > scrolls, I (my program) am *much* faster than the user can ever be. So there > is no problem. If you (your program) are not drawing faster than the user > can scroll, perhaps there is a need to think about why that is. But, as I > say, I do not know enough to be helpful with that. > > Again, I would repeat that the ScrollViewSuite example seems to me to be > doing something similar to what you describe, so perhaps it could be useful. > > I'm sorry I'm not more help - m. > > -- > matt neuburg, phd = m...@tidbits.com, http://www.tidbits.com/matt/ > pantes anthropoi tou eidenai oregontai phusei > Among the 2007 MacTech Top 25, http://tinyurl.com/2rh4pf > AppleScript: the Definitive Guide, 2nd edition > http://www.tidbits.com/matt/default.html#applescriptthings > Take Control of Exploring & Customizing Snow Leopard > http://tinyurl.com/kufyy8 > RubyFrontier! http://www.apeth.com/RubyFrontierDocs/default.html > TidBITS, Mac news and reviews since 1990, http://www.tidbits.com > > > > _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
