On Nov 7, 2010, at 22:34:41, Greg Guerin wrote: > Rick Mann wrote: > >> Note that the precision of all this isn't so high as to make this "hard" >> real time. It just has to be good enough that a person watching the display >> and comparing it (visually) to an accurate clock would consider them to be >> synchronized. I'd like to do no worse than 100 ms. >> >> Any ideas? > > > I can tell you from experience that 100 ms will be visually noticeable. More > than you might think. > > In any case, to get the display to update ON the second you'd have to change > the labels and such BEFORE the second actually occurs. > > And you'd have to account for any discrepancy between the software's clock > and the unidentified "accurate clock". If the software doesn't know what the > accurate clock is, how would it know its accuracy, so how could you know that > a person won't see a difference, even if the display is exactly "on the > second"?
Well, I've implemented an SNTP client to improve the clock accuracy. I guess what I'm really asking is, how long after I exit the run loop before drawing is complete? And yeah, I'd like to do better than 100 ms. -- Rick _______________________________________________ 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
