Re: [Meego-handset] About missing usage of Accounts SSO
Hi, -Original Message- From: Eklund Jukka Sent: 29 March, 2011 15:43 Subject: Re: [Meego-handset] About missing usage of Accounts SSO Hi Alberto, ma...@users.sourceforge.net wrote: Why is it so? Is it in the roadmap to use it? On Tue, Mar 29, 2011 at 1:22 PM, Alberto Mardegan Note that handset is in a bit of a state of flux at the moment. The MeeGoTouch handset applications (as far as I know) don't really have any active development, and as such, have bitrotted quite a bit. There is some discussion at the moment about moving to the new 'unified'/tablet UX recently released by Intel, and undergoing active development. Perhaps you'd be better off checking it out? I understood the current Handset UX actually uses that stuff? See eg. Social accounts applet that is in Settings application? Only buteo and qmf seem to use accounts sso. -- Mikko ___ MeeGo-handset mailing list MeeGo-handset@lists.meego.com http://lists.meego.com/listinfo/meego-handset
[Meego-handset] [PATCH] Fixed: BMC#14948 The system time is displayed before the call is actived in caller info bar Signed-off-by: Arun Ravindran ext-arun.1.ravind...@nokia.com
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 callitemview.
---
src/callitemview.cpp |7 +--
src/callproxy.cpp|3 ++-
2 files changed, 7 insertions(+), 3 deletions(-)
diff --git a/src/callitemview.cpp b/src/callitemview.cpp
index b7ed2ae..cb1b39b 100644
--- a/src/callitemview.cpp
+++ b/src/callitemview.cpp
@@ -128,8 +128,11 @@ void CallItemView::initLayout()
void CallItemView::updateDurationLabel()
{
-QTime t = QTime(0,0).addSecs(m_controller-duration()/1000);
-durationLabel()-setText(t.toString(Qt::TextDate));
+//modify the duration string only if there is a valid data.
+if(m_controller-duration()) {
+QTime t = QTime(0,0).addSecs(m_controller-duration());
+durationLabel()-setText(t.toString(Qt::TextDate));
+}
}
void CallItemView::updateStatusLabel()
diff --git a/src/callproxy.cpp b/src/callproxy.cpp
index 5d1689c..76b3213 100644
--- a/src/callproxy.cpp
+++ b/src/callproxy.cpp
@@ -98,7 +98,8 @@ QDateTime CallProxy::startTime() const
int CallProxy::duration() const
{
TRACE
-return m_startTime.time().elapsed();
+// Returns the elapsed duration in seconds
+return m_startTime.isValid()?m_startTime.time().elapsed()/1000:0;
}
QString CallProxy::reason() const
--
1.7.0.4
___
MeeGo-handset mailing list
MeeGo-handset@lists.meego.com
http://lists.meego.com/listinfo/meego-handset
Re: [Meego-handset] [PATCH] Fixed: BMC#14948 The system time is displayed before the call is actived in caller info bar Signed-off-by: Arun Ravindran ext-arun.1.ravind...@nokia.com
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
