Skip to Content (Press Enter)
2018-11-09 09-14-06
Gonçalo Almeida
77Views
9Comments
Richwidgets Input Calendar on iPad
Question
OutSystems Widgets
Hi all,

Using version 9.0.1.50.
I have a screen with the Input_Calendar widget that shows completely different on the iPad. I think it's using the default date picker and not the Input_Calendar.
Is there a way for me to "force" the browser to use the Input_Calendar?

regards
0
0
28 Jan 2016
Copy Link
2020-09-15 13-07-23
Kilian Hekhuis
 
MVP
Hi Gonçalo,

Just to make sure: the same eSpace looks ok when viewed on another device? Is it just the iPad or all Apple devices? Also on iOS? How about Android, or Windows?
0
0
29 Jan 2016
Copy Link
2018-11-09 09-14-06
Gonçalo Almeida
Hello Kilian,

Yes, it look ok on every device. I've tested on many devices.
It only changes on iPad.
0
0
29 Jan 2016
Copy Link
2020-09-15 13-07-23
Kilian Hekhuis
 
MVP
That's decidely weird. Unfortunately, I know little about iPads... I hope someone from OS can weigh in.
0
0
29 Jan 2016
Copy Link
2018-06-04 08-06-09
Peter Van Den Ochtend
I experience the same problem. The input_Calender function changes on the ipad.
When I use it in a form and save the page. It saves the date/time value with +1 hour (!!)... 

When I test it using form validation and leave a different mandatory field empty and try to save it. It raises the time with +1 hour with every click... I don't think that should work like that...

Unfortunately it isn't possible to debug an ipad app :(
0
0
15 Mar 2016
Copy Link
2020-09-15 13-07-23
Kilian Hekhuis
 
MVP
That seems like a DST problem? Anyway, OS should way in here.
0
0
15 Mar 2016
Copy Link
2018-06-04 08-06-09
Peter Van Den Ochtend
I've opened a support case with them because this component is supported. I will keep this thread updated with the results!
0
0
16 Mar 2016
Copy Link
2016-07-14 09-30-08
Douglas Wilkinson

Did OutSystems get back to you on this? 

I'm having a similar problem with iPad. Looking different I can cope with, but it also takes no notice of the "InitialDate" setting, so always opens on today's date. I have a requirement on a DOB field that the calendar opens on today's date but 21 years in the past. So I've set Initial date to:

AddYears(CurrDate(),-21)

but iPad is not playing ball. Everything else works fine. I'm using v9.0.1.75

0
0
07 Jun 2017
Copy Link
2018-11-09 09-14-06
Gonçalo Almeida

Douglas Wilkinson wrote:

Did OutSystems get back to you on this? 

I'm having a similar problem with iPad. Looking different I can cope with, but it also takes no notice of the "InitialDate" setting, so always opens on today's date. I have a requirement on a DOB field that the calendar opens on today's date but 21 years in the past. So I've set Initial date to:

AddYears(CurrDate(),-21)

but iPad is not playing ball. Everything else works fine. I'm using v9.0.1.75


If I remember correctly, this happens because the Input_Calendar is completely substituted by the iPad version of the widget.

0
0
07 Jun 2017
Copy Link
2016-07-14 09-30-08
Douglas Wilkinson

Gonçalo Almeida wrote:

Douglas Wilkinson wrote:

Did OutSystems get back to you on this? 

I'm having a similar problem with iPad. Looking different I can cope with, but it also takes no notice of the "InitialDate" setting, so always opens on today's date. I have a requirement on a DOB field that the calendar opens on today's date but 21 years in the past. So I've set Initial date to:

AddYears(CurrDate(),-21)

but iPad is not playing ball. Everything else works fine. I'm using v9.0.1.75


If I remember correctly, this happens because the Input_Calendar is completely substituted by the iPad version of the widget.

Okay, thanks Gonçalo. I'll let my client know that it's a limitation on the iPad. It's quick and easy enough to scroll back the year anyway on iPad, unlike on the normal widget.


0
0
07 Jun 2017
Copy Link
Community GuidelinesBe kind and respectful, give credit to the original source of content, and search for duplicates before posting.