On Tue, 29 Mar 2011 16:26:21 +0300 ext-arun.1.ravind...@nokia.com wrote: > From: Arun Ravindran <ext-arun.1.ravind...@nokia.com> > > The m_updateTimer, updates the call duration read from the Callproxy > to the callitemview. When the call is dialing, or alerting and if the > timer is elapsed it reads the starttime property (which is NULL), and > gets the elapsed value from it, even if it is not valid, which > results in wrong time string (which is not the actual duration of the > call) updated to the callitem. > > Fixed by checking the validity of the m_startTime, before returning a > duration and also checking it before updating the duration test in
Arun, First, thanks for this patch... as we discussed on IRC, it is really just part of a larger fix to overall elapsed time calculations. I spent the day looking into this and ended up doing a bunch of changes, including a portion of this patch, though it needed to be modified due to my additional fixes. So, I believe the entire problem (including the elapsed time computations and more robust and centralized time/string conversion throughout) is now resolved with commit d7e1749c0afb18 [1]. Regards, Shane... [1]https://meego.gitorious.org/meego-handset-ux/meego-handset-dialer/commit/d7e1749c0afb18 _______________________________________________ MeeGo-handset mailing list MeeGo-handset@lists.meego.com http://lists.meego.com/listinfo/meego-handset
