i realise that this issue has most likely been done to death before i arrived on the android scene. i'm more looking for suggestions on logic flow than having a big moan about the lack of a modal show-dialog call.
AFAICS, the only way of handling input to a basic text input dialog is to register an onClick handler and listen for the OK button. but this means that anything you want to do following a successful dialog transaction has to be in onClick(). and this could be anything - in my case, a potentially long server transaction. during this time, the dialog is still up, making things look a bit ugly, and other UI interactions won't work inside onClick(). so what are people doing in this situation? i thought of queueing up a progress dialog in onClick(), then starting a thread doing the business. is this the accepted way of doing it? ideally, of course, there would be a JOptionPane equivalent, which blocks until the user dismisses the dialog, returning the number of the button that completed the transaction. then the client code could proceed with whatever it wanted to do, unhindered by the confines of onClick(). tx --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
