After the 6.0 upgrade, the code in the Input_Calendar button was moved from the OnChange to the OnClick.  If you change the button code to "onclick()" instead then the problem will be resolved.

Nope, that's not what I mean.
With v6 in the richwidget you can also have a button to trigger the calendar to open, not clicking in the input field. By personal request :-) ....
That all works like a charm. However if then a date is selected, the onChange of the input field is not triggered ...

This is just what I need too. A button to trigger the calendar to open. The users I'm working with want to choose how they fill in a date with IE, whether they wanted to type the date themselfs or use the calendar input widget. 

I was able to duplicate this.  In the extended functions I set the onblur event to be "onchange()" and the event was triggered correctly after a date was selected from the calendar.   The "OnUpdate" needs to be set to the Input Id as well.

Hi all,

Note: I didn't try anything out, didn't even try to replicate the problem.

But just as a warning before everyone starts setting javascript events to detect changes: Native browser events are NOT triggered when values are changed by javascript.
Also events like onblur usually have browser specific behaviors.


That said, if that is the current widget behavior is not triggering the On Change action built-in on the platform, I recommend creating a small sample eSpace and submitting it as an issue.

Regards,
João Rosado

@Rebecca: to me this seems like a bug in the widget !

@Joao: then Outsystems needs to fix the component to work properly. Outsystems knows now :-)
But keep on looking in the mail. A sample OML is coming your way... by the way to me this is not tested properly before it has been sent out to the publie :-)

Thanks rebecca,
I've just pointed support to this issue.

Hope they'll understand and fix it :-)

News from support:

We’ve managed to reproduce the reported behavior.
In order to fix it in future revisions of the Platform, we’ve forwarded this information to our R&D.
In the meanwhile, the workaround suggested in the forums can be used to overcome this problem.

@Outsystems: Any news on this item ??

Hi Joop,

I did a fix for it after my last reply here.
It's already on the 6.0.1.19, so I guess It will be available on the next 7.0 revision also.

Regards,
João Rosado

Hi,

Don't have a example eSpace at the moment with it, but it doesn't need anything special to work.

Just make sure you are using the RichWidgets from the SystemComponents distributed on 6.0.1.19+
(Note that at the time of this post there is no 7.0 release with that fix)


Regards,
João Rosado

Ok, extracted the richwidgets.
It's a small change.

Thanks!