On Jun 16, 2010, at 8:17 AM, Tony P <[email protected]> wrote: > Thanks for all the responses folks. > > On 15 Jun 2010, at 7:22 pm, Corbin Dunn wrote: > >> Do the height calculations in the bounds change, and then call the >> "noteHeight.." method all in the same run loop stack; that will probably fix >> your problem. > > Beautiful, works like a dream. Many, many thanks for that, you're a superstar! > >> Even though it is fast, however, a table with 200,000 rows is excessive. >> There is no way a user can realistically use all those rows without some >> sort of filtering/searching. I would consider re-doing your UI to have a >> "more results" button, akin to the Finder spotlight search results. > > It does have a search, and I would agree, but arbitrary browsing is required > (even from the search which just scrolls to the results). Unfortunately it's > a PC->Mac port and you'll have to drag me through hot coals before I'll be > happy with a Mac version that seems somehow inferior to the PC version. It's > an iPhone version next though, so I'll definitely have to re-think the UI for > that.
“Inferior” does not mean “fewer things on the screen.” Now is your opportunity to exploit the Mac's less-is-more conventions to better the experience and produce a superior product. This might in turn inform the Windows side of the product, and so forth. --Kyle Sluder_______________________________________________ Cocoa-dev mailing list ([email protected]) 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 [email protected]
