>> Note that you are free to modify any part of the widget hierarchy (or >> models used by the widgets) outside the event loop as long as you >> register your attach your thread to the application instance and grab >> the application's update lock (in WApplication: attachThread() and >> updateLock()). These modifications will be synchronized with the >> browser on the next event, so you could for example chose to attach to >> the WTimer a no-op call back routine. > > Speaking about WTimer, I think its implementation is wrong on Unix and > could be more precise on Windows (although I'm not sure more precision > is required; I've not checked if Wt::Time is used server-side).
I haven't looked, but is there any reason that boost::asio::deadline_timer isn't being used to back WTimer? I'm pretty sure this addresses all of the concerns listed below. -sc http://www.boost.org/doc/libs/1_41_0/doc/html/boost_asio/reference/deadline_timer.html -- Sean Chittenden [email protected] ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ witty-interest mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/witty-interest
