I tried the SuperGetPassword statement to see how it would create a dialog. The code for that included an ‘Unlock’ button. Since then, my Info(“DialogTrigger”) responses have been incorrect.
After having tried the SuperGetPassword dialog, the response from all buttons in dialogs from Info(“DialogTrigger”) was always ‘Unlock’, regardless of the name of the button that was pressed.
I then restarted Panorama and using Info(“DialogTrigger”) now responds with a dialog with no info, just the OK button.
This happens as well on a New database with the same no named title.
After first posting this, I then added a ~1x2 rectangle. I named it 1x2BlkSquare with its procedure being the same ‘Junk’. I clicked on it, and it returned 1x2BlkSquare. But then when I clicked on the segmented buttons, they too responded with 1x2BlkSquare. Each object responds with the same 1x2BlkSquare response.
Evidently because a Segmented Button returns the name of the button pressed to the field or variable that is linked to it it does not bother to trigger the Info(“ClickedObjectName”).
But if I had several segmented buttons that each had a Left Right Center, that would not be good. I am sure that it should have triggered the “ClickedObjectName”. Checking to see if a reinstall is in order.
Gary is correcto. I’m not sure that this is the way I’d do it as I may have several identical Segmented Buttons that I’m trying to know which one was just clicked, but it is what it is.
As for the “DialogTrigger”, that is specfically for Dialogs. Period. It may have been a dialog hours ago, but it is the last dialog. And ordinary buttons do not ordinarily create dialogs.
If there has been no Dialog since Panorama was started up, there may be no text in the Info(“DialogTrigger”) response.
As for the ‘Topic List’, perhaps there was something in the past. Can’t say for sure.
Which furthers my difficulty in really being clear of what a “DialogTrigger” really is. I had originally intended to create a dialog but what was going to be my equivalent of an ‘ok’ button and also what was going to be my ‘cancel’ button were never going to be triggering the info(‘DialogTrigger’) that I was imagining. It was going to look like a Dialog to me, but alas, not Panorama, while the ‘Topic List’ qualified as a dialog. Hmmm.
Dang. Now we are back to inconsistency. I just started up my ‘Junk’ test file again with the segmented button and it gave me the ‘no text’ dialog with only the Panorama OK button.
But if I add a Push Button, set the ‘Default Button’ attribute, then my ‘ClickedObjectName’ works for the Push Button, the Rectangle, and the Segmented button merely responds with the same name as what the previous objects name was. The previous object’s name is used instead of the Segmented Button’s name.
It is the inconsistency (or perceived inconstency) that is making this difficult to maneuver.
When I create a Push Button, and set the ‘Default Button’ attribute, I was expecting that ‘Default Button’ to then make that form a Dialog with the ‘DialogTrigger’ be my ‘Default Button’. Clearly a poor assumption.
First of all, you’ve discovered a bug in Segmented Buttons. When clicked, they should set up the underlying data for the info(“clickedobjectid”) and info(“clickedobjectname”) functions, but they don’t. So these functions will return the results for whatever object was pressed previously (if any). This bug will be fixed in the next release.
I don’t understand this sentence. You make it sound as if using this function makes a dialog appear, but all it does is return the name of a button.
This is definitely not true. For example, if I run this code:
let thePassword = ""
supergetpassword thePassword,{buttons="Unlock;Cancel"}
alertnoyes "choose"
message info("dialogtrigger")
the message alert will display either Yes or No, not Unlock.
Ok, I think I see at least part of the problem. You made me think that info(“dialogtrigger”) worked until you used supergetpassword, but I’m thinking that this function never worked the way you expected. And I can see that if you just looked at the documentation for info(“dialogtrigger”) on it’s own, it’s a bit misleading. This function only works with specific pre-defined standard alerts and dialogs that are included with Panorama. It does not work with custom dialogs you have created with a Panorama form using the rundialog statement. I have just revised the documentation to hopefully make this more clear.
