Developer Portal | RhoElements Date bug

Submitted by Ord Millar on July 23, 2012 - 10:52am

Tags:

Using RhoElements on Windows CE:

var theDate = new Date();

theDate will have the date that the RhoElements App started running, not the current date. The time portion is also incorrect, but does keep advancing (there is a discrepancy between the time returned and the system time, but it seems to be small, about 30 minutes). The only way I have found to get the date to update is to exit and re start the app.

We have found this with the runtime versions 1 and 2, on both an MC3100 and MC3190.

May 4, 2019 - 7:42am

(Reply to #6) #1

Pietro Francesc...

Ord,even my test on the ES400

Ord,

even my test on the ES400 show the stuck time.

This morning the time was in sync but after 4/5 hours moved just few minutes.

Pietro

Vote:

July 16, 2012 - 3:55pm

Ord Millar

Something else:Method

Something else:

Method toLocaleString() outputs the wrong month (one month early).

toDateString(), toUTCString() and toISOString() show the correct month.

Vote:

July 16, 2012 - 3:51pm

(Reply to #2) #3

Pietro Francesc...

Hi Ord,the small test that

Hi Ord,

the small test that follows works correctly with RE 1.0.3.11 on an ES400. Well, pressing the Update button, you see that the DateTime is correct. But you are right, the toLocaleString() report the wrong month (one early).

Sample code:

<html>

<head>

<title>Date Sample</title>

function fnUpdateDate() {

var currentTime = new Date()

var month = currentTime.getMonth() + 1

var day = currentTime.getDate()

var year = currentTime.getFullYear()

var myContent = month + "/" + day + "/" + year + "<BR>" + currentTime.toLocaleString()

//alert(myContent);

document.getElementById('para').innerHTML = myContent;

}

</script>

</head>

<body>

</html>

~Pietro

Vote:

July 16, 2012 - 4:30pm

(Reply to #3) #4

Ord Millar

Pietro,you will have to keep

Pietro,

you will have to keep that test page open for 24 hours to see if the problem is happening in your installation.

Regards,

Ord

Vote:

July 16, 2012 - 5:13pm

(Reply to #4) #5

Ord Millar

The problem is in fact

The problem is in fact different than I first described.

What happens is that the MC3100 goes to sleep after a period of inactivity, and the time within RhoElements stops advancing. Exiting and re-entering elements re synchronizes the clock with the system clock.

To reproduce, it is sufficient to start RhoElements, check that the time is correct, then power down (without exciting elements) for a few minutes. Power back up, and observe that the time shown in elements is no longer correct.

Vote:

July 16, 2012 - 5:18pm

(Reply to #5) #6

Pietro Francesc...

Ord,what OS is your MC3100

Ord,

what OS is your MC3100 using, CE6 or WM6.5? and which BSP?

I've done my testing on an ES400 with WM6.5 and BSP31.02 and, at this moment, I don't see this issue.

~Pietro

Vote:

July 17, 2012 - 6:52am

(Reply to #7) #7

Ord Millar

Thanks, I am glad to hear you

Thanks, I am glad to hear you can reproduce it. Now I need to find a solution, because our applications requires correct time stamps when we store information.

P.S. We used windows CE 6.0

Vote:

July 24, 2012 - 7:09am

(Reply to #8) #8

Ord Millar

Do you know if there are

Do you know if there are plans to correct this, and when that might happen?

Vote:

July 17, 2012 - 3:25pm

(Reply to #9) #9

Ord Millar

I have found a temporary

I have found a temporary solution to this problem:

The WEBSQL engine uses the system time, not the RhoElements time, so we can query the database to get the correct time:

 db = openDatabase('odm_ts','1.0','TimeStamp',1*1024*1024);
            
              db.transaction(function(tx){        
                    tx.executeSql("SELECT datetime('now','localtime') as t",[],
                    function(tx,result){
                        time = result.rows.item(0)['t'];
                        alert('Database has: '+time);                        
                    },
                    function(tx,error){
                        alert('Error:'+error.message);  
                    })      
    });

Vote:

July 24, 2012 - 10:16am

(Reply to #10) #10

Ord Millar

The above fix does not work

The above fix does not work for RhoElements 1.0.2.3

In the earlier version, SELECT datetime('now','localtime')

return a bad value. For example, now it is saying "6461-12-31 05:36:13"

So, we can't use this work around.

Vote:

July 25, 2012 - 9:48am

(Reply to #11) #11

Pietro Francesc...

Ord,Why are you using v1.0.2

Ord,

Why are you using v1.0.2.3?, there is newer release of RhoElements 1 and then the shared runtime of version 2.

Version 1.0.3.11 is available on the support site:

http://support.symbol.com/support/search.do?cmd=displayKC&docType=kc&externalId=13526&sliceId=&dialogID=409290709&stateId=1%200%20409280838

Pietro

Vote:

July 25, 2012 - 10:22am

(Reply to #12) #12

Ord Millar

Hi Pietro,I have tested

Hi Pietro,

I have tested originally with 1.0.2.3 because that is what the client has installed. I checked here with the new version and found:

v1.0.3.11 does have the correct time in the WEBSQL engine, but wrong time from the javascript Date object. Also still has the error of showing one month early in the Date.toLocaleString() method. Version 2 behaves the same.

We will ask our clients to upgrade to 1.0.3.11 and put in a patch to get the time from the database until there is a fix to the runtime.

Vote:

May 4, 2019 - 7:43am

#13

Anonymous (not verified)

Hi,Please forgive that I

Hi,

Please forgive that I haven't read the entire thread here but reading your first post I recognise the issue.

Unfortunately this was fixed just too late to make it into our 2.1 drop due out next week The fix for this will be in 2.2.

Regards,

Darryn.

Vote:

Search form

RhoElements Date bug