iPhone pickDate

[stevenchalmers]

I must be missing something with iphonePickDate tutorial because the starting value is today, rather than the second parameter I give it.

According to the dictionary the iphonePickDate syntax is: iphonePickDate [style, current, start, end, step]

Note that the second parameter is called "current" rather than "selected".

If I call iphonePickDate with this code the date that is first displayed is today, not 07/29/11.

Code: Select all

put "07/29/2011" into tSelected // the date and time selected by default
put "07/20/2011" into tRangeStart // the minimum date and time that can be selected
put "08/01/2011" into tRangeEnd // the maximum date and time that can be selected
put 5 into tInterval

// convert the dates into seconds since the UNIX Epoch
convert tSelected to seconds
convert tRangeStart to seconds
convert tRangeEnd to seconds

// launch the date and time picker
iphonePickDate "dateTime", tSelected, tRangeStart, tRangeEnd, tInterval

I have the same issue if I use "date" as the first parameter too.


Steven (Colorado, USA)

[Dixie]

Hi...

I am having the same problem... it looks like you can have any day as long as it is today!

be well

Dixie

[CALL-151]

Off topic, I know, but how'd you learn that 4.6.4 had been released? I found out by inference after reading this topic. There's gotta be a better way.

[Jellicle]

So you didn't get the email? Contact RunRev to make sure you are on their mail list.

Gerry

[CALL-151]

Will do, thanks. I get the newsletter and several/month from sales@runrev, but no 4.6.4 announcement.

BTW, after briefly playing around with different settings in pickDate I have the same issue.

[Nikovash]

After reading this post I went and tried out the iPhone Date Picker command and experienced the same result. Interesting enough I had a weird result come to light that I just didn't think of. Effectively the date 1/1/1970 is actually 28800 in seconds, because I am at GMT -8:00 hours of trying to come up with a conversion to offset for this was not needed and I was simply overreacting to what should happen in the first place. Silly time zones!

[CALL-151]

Just checked version 4.6.4 build 1453 to see if this is resolved. It isn't.