[mateen_maldar]

Hi,

This is my second post on python, well i tried to use the date .. like this..

import appuifw

appuifw.query(u"Type a date:", "date", u"01/01/2008")

Everytime i run it must display 01/01/2008 inside the dialog instead it displayes 01/01/1970, on emulator i tested this..

Does anyone know why this is behaving like that...

i'm using S60_3rded_Fp2 ...

i just was trying to learn python...

Regards,
Mateen Maldar

[croozeus]

Hi Mateen,

Originally Posted by mateen_maldar

Hi,

This is my first post on python,

I don't think so this is your first post on Python Forum

want to build python src

Originally Posted by mateen_maldar

well i tried to use the date .. like this..

import appuifw

appuifw.query(u"Type a date:", "date", u"01/01/2008")

Everytime i run it must display 01/01/2008 inside the dialog instead it displayes 01/01/1970, on emulator i tested this..

Does anyone know why this is behaving like that...

i'm using S60_3rded_Fp2 ...

From the PyS60 documentation :

Date and Time:
Unix time, seconds since January 1, 1970, 00:00:00 UTC (Coordinated Universal Time), is generally used
as the time format in the Python for Series 60 APIs described in this document.

So it doesn't matter if you write,

appuifw.query(u"Type a date:", "date", u"01/01/2008") 
or 
appuifw.query(u"Type a date:", "date", u"Mateen")

Date will always start from January 1, 1970.

And for time it doesn't matter if you write the following,

appuifw.query(u"Type time:", "time", u"09:00") 
or
appuifw.query(u"Type time:", "time", u"01/01/2008") 
or 
appuifw.query(u"Type Time:", "time", u"Mateen")

Time will always start from 00:00:00 UTC.

Originally Posted by mateen_maldar

i just was trying to learn python...

Great to have one more FNC interested in PyS60

Best Regards,
Croozeus

[gaba88]

hi mateen
great to see you in the python discussion boards

[mateen_maldar]

Hi,

I will answer myself again asusual, as i'm not satisfied with the below explanation..

This is the exact reason for this behaviour.

There are two standard representations of time. One is the number\n\
of seconds since the Epoch, in UTC (a.k.a. GMT). It may be an integer\n\
or a floating point number (to represent fractions of seconds).\n\
The Epoch is system-defined; on Unix, it is generally January 1st, 1970.\n\
The actual value can be retrieved by calling gmtime(0).\n\

I Hope someone has more explanation about this...any Pointers are appriciated

Regards,
Mateen Maldar

[shubhendra]

I think thats due to implementation, as done in appuifwmodule.cpp where implementation is like this,

case R_APPUIFW_DATE_QUERY:

case R_APPUIFW_TIME_QUERY:

  time = (rid == R_APPUIFW_DATE_QUERY) ? epoch_local_as_TReal() : 0.0;

[aaaaapo]

Originally Posted by mateen_maldar

import appuifw
appuifw.query(u"Type a date:", "date", u"01/01/2008")

Default value for "date" and "time" queries MUST BE a FLOAT.
Confusing, isn't it? But it makes sense if you think what those queries return: epoch as a float (e.g. "1219229900.0").

So try this:

import appuifw, time
appuifw.query(u"Type a date:", "date", time.time())
appuifw.query(u"Type a time:", "time", time.time())
print time.time()