 |
Registered Users must be logged in to 'MyAccount' to add a Comment - Log In Here |
| After Logging In, Click Here to Refresh This Page |
| onSelect | This page was last modified over 30 day(s) ago and has 0 comment(s)
|
| Back to Dialogs Class Summary |
| Availability |
| Windows, Mac OSX, Linux |
| Usage |
| mdm.Dialogs.onSelect |
| Parameters |
| Returns |
| Description |
| event called when native dialog invoked with mdm.Dialogs.promptAdvAsync or mdm.Dialogs.promptModalAsync is closed by user explicit action - that is when e.g. "OK" button is clicked and dialog returns control to application |
| Notes |
| There are two ways to listen for events in 4.0: #1 using "onEventNameFunction" - callback based handlers introduced in {mdm} 2.0 #2 using IEventListener model based on Events introduced in 4.0. No matter what implementation you would use either callback and listener handler would have to use single-argument defintion as in below sample: // callback based handlers mdm.Appllication.onAppChangeFocus = function(event:Event):void { // proceed with event }; // handlers based on IEventListener model function onAppChangeFocusHandler(event:Event):void { // proceed with event }; |
| Example Code |
| // callback version mdm.Dialogs.onSelect = function(event:Event):void { // dialog was closed/confirmed }; mdm.Dialogs.promptAdvAsync(messageText, "alert"); // event-listener model function onSelectHandler(event:Event):void { // dialog was closed/confirmed }; // mdm.Dialogs.addEventListener("onSelect", onSelectHandler); mdm.Dialogs.promptAdvAsync(alertMessageText, "alert"); |
| mdm.Dialogs Class Example Downloads |
| No Example Downloads Available |
|
Registered Users must be logged in to 'MyAccount' to add a Comment - Log In Here |
| After Logging In, Click Here to Refresh This Page |