Wasn't sure if it when this occurred - just noticed it yesterday when I was doing something else. It seems to me that it should not allow a click - matching the behavior of the main menu. From a user's perspective, they may think they clicked on something that should do something ... so it may confuse the user.
Jason Van Anden http://www.bubblebeats.com http://www.twitter.com/bubblebeats On Sat, Oct 17, 2009 at 6:45 PM, Mark Murphy <[email protected]>wrote: > > Jason Van Anden wrote: > > I am setting setEnabled = false for a Context Menu item. > > > > The item appears grayed out ... but I can still click on it. When I do, > > the menu closes. > > > > This does not seem to like the correct behavior to me. > > > > Is this a bug or a misunderstood feature? Anyone else experiencing this? > > I can tell you that I see the same behavior in 1.5 and 1.6. I hadn't > tried a disabled context menu item before. > > I can see arguments either way as to whether it is correct behavior, so > I do not know whether it is a bug or not. > > -- > Mark Murphy (a Commons Guy) > http://commonsware.com | http://twitter.com/commonsguy > > _Android Programming Tutorials_ Version 1.0 In Print! > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
