On 11 May 2011 15:14, Zanarotti Michele <[email protected]> wrote:
> Ibendlin, sometimes menu items are based on a situation, as money to buy > something (think of a game). I want to show > to the user what he/she can buy, but make the button inactive because the > overall money is not enough. I saw pratically every > game/site doing this. > This is wrong approch then. Disabling button only tells "you can't buy". But it do not tell "why". It would then be better to leave button/menu available but pop up a dialog (or whatever) saying that this item requires XXX of currency while you have 0 or YYY (which is ZZZ short). This is even better as, assuming your goal is to sell, you can easily add next button to that dialog/activity to redirect user to i.e. checkout/paypal etc. so he could add funds to the account while on shopping spree instead of just teling him "no. get out". Android is graying out the item, but the nonsense is to make it clickable. > Furthermore, when a disabled button is clicked > the onItemSelected event is not launched (as desired), so , why closing the > menu ?? > Do agree it's counter intuitive. It may also be a bug (or works by design even when not in the best manner). Considered filling bug report at b.android.com? Regards, Marcin Orlowski *Tray Agenda <http://bit.ly/trayagenda>* - keep you daily schedule handy... *Date In Tray* <http://bit.ly/dateintraypro> - current date at glance... WebnetMobile on *Facebook <http://webnetmobile.com/fb/>* and *Twitter<http://webnetmobile.com/twitter/> * -- 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
