Profound Logic Forums

Is there a way to show/bring up the calendar in a date widget when a button is clicked?

In the current release, you can attach the following to the button's onclick event:
Where "Date1" is the id of the date widget.

In the next release, we will publish a more formal API to accomplish this. It will be called pui.showCalendar().

Hi Alex,

I placed the "pui.showCalendar("DateID")" method in the onClick of a button, with the ID of a date widget as its parameter, but it didn't work. When I click on the button nothing happens.

I'm using the latest release of profoundui (4.1.6).

Hi could I have some help. I tried: pui.showCalendar("DateID") and it isn't working. I have it in the onclick of a button. when I click the button, nothing happens.

Does it work if you use the older method -- getObj("Date1").calimg.click()?

Hi, "getObj("Date1").calimg.click()" didn't work either.

I've noticed that you can work around this problem by changing your onclick to this: Does that work for you?

I'm not sure if that's a "good" way to make it work, but it seems to work for me. I will have to check with colleagues and see what they think.

Hi scott, that method is working for me in the browser, but it isn't working in my mobile tablet or phone. I am using the profound ui mobile client.

I still can't get "pui.showCalendar("Date1")" to work in the mobile client. help

The original problem occurs because of the way the calendar popup works. When the calendar comes up, you can "click away" (click any area outside of the calendar popup) to close it.

The problem is that when you put a button on the screen that opens the calendar, you start by clicking the button. The first thing your click does is open the calendar box, but then the calendar box sees you clicking outside of the popup (because you're in the middle of a "click" event on the button) and immediately closes the popup.

The setTimeout() worked around this problem by adding a slight delay to opening the popup, so that it occurs after the button click is complete.

Not sure why this wouldn't also work in the mobile client, though. You could try preventing the default action for the click to the button and see if that helps?