![]() |
2012-07-22
, 06:52
|
Posts: 650 |
Thanked: 619 times |
Joined on Nov 2009
|
#222
|
windows.push("trafficDetailsPage.qml")'
TrafficEventHeader 1.0 TrafficEventHeader.qml
![]() |
2012-07-22
, 07:27
|
Posts: 458 |
Thanked: 783 times |
Joined on Jan 2010
@ France
|
#223
|
Ouch, you're right. Thanks for catching this bug.
I found that the return value of Units.getReadableTime(duration) can be in "hr:min" format. This confuses the if (readableDuration.value > 0) loop. Commenting out the sanity checking makes the time display correctly. Please verify this solution if you can, if it doesn't introduce new bug, then I think this is an easy fix and can be pushed to unstable patch.
![]() |
2012-07-22
, 09:33
|
|
Posts: 956 |
Thanked: 2,628 times |
Joined on Nov 2011
|
#224
|
![]() |
2012-07-22
, 13:52
|
Posts: 90 |
Thanked: 35 times |
Joined on Jan 2012
|
#225
|
Hi sony123 !!!
I have updated my full patch with your latest discover in section Unstable ;-)
A++
![]() |
2012-07-22
, 14:40
|
Posts: 78 |
Thanked: 135 times |
Joined on Jul 2012
|
#226
|
Ouch, you're right. Thanks for catching this bug.
I found that the return value of Units.getReadableTime(duration) can be in "hr:min" format. This confuses the if (readableDuration.value > 0) loop. Commenting out the sanity checking makes the time display correctly.
![]() |
2012-07-22
, 15:45
|
Posts: 458 |
Thanked: 783 times |
Joined on Jan 2010
@ France
|
#227
|
Hi colin.stephane
I think you got carried away with the commenting!
The unstable patch as-is doesn't work. You commented out the definition for the variable distTime at the same time as the 'sanity-check'. If that is left in there it seems to work - at least trying to navigate 700km on my sofa!
![]() |
2012-07-22
, 16:36
|
|
Posts: 5,339 |
Thanked: 4,133 times |
Joined on Jan 2010
@ Israel
|
#228
|
![]() |
2012-07-22
, 16:40
|
Posts: 290 |
Thanked: 269 times |
Joined on Apr 2010
@ Brussels
|
#229
|
![]() |
2012-07-22
, 16:54
|
|
Posts: 956 |
Thanked: 2,628 times |
Joined on Nov 2011
|
#230
|
I found that the return value of Units.getReadableTime(duration) can be in "hr:min" format. This confuses the if (readableDuration.value > 0) loop. Commenting out the sanity checking makes the time display correctly. Please verify this solution if you can, if it doesn't introduce new bug, then I think this is an easy fix and can be pushed to unstable patch.
Last edited by sony123; 2012-07-22 at 04:43.