NativeDialogs
NativeDialogs copied to clipboard
mateuszmackowiak
NativeAlertDialog for Windows
The old "NativeAlert" library was compatible with Windows (at least the regular NativeAlert class).
It would be desirable to have that compatibility back in the NativeAlertDialog class of the "NativeDialogs" library (and ideally MacOS X too).
+2. I signed up just to post this. I spent an hour trying to figure out why the code, following their own example, wasn't working during desktop testing. Pushed to the device and voila!
Please bring it back to the desktop. For now I'll use the original.
+3 You can include the old ANE in your project, but then you are not able to publish your app to iOS anymore. You can only have NativeAlert OR NativeDialog included in your project when exporting release build for iOS. The downside with including both ANEs is that you have to take care to import the correct class (only minor differences between the ANEs). Also, the code becomes a bit messy because if you want to check which button was clicked after the alert closes you have to check from which ANE the NativeDialogEvent-class is and then casting the event to that class.
Why was this feature removed in the first place?
I'm surprised this is still an issue. I guess some of the new toasts and such were too hard to implement in desktop and just got nixed. Would be good if that were just replaced with a simple dialog though like "TOAST would be displayed here on mobile" -- end of story.Heck, a Toast can easily be drawn in AS.