[ALOY-463] Alloy doesn't allow requiring of an Android Menu
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | Medium |
| Status | Closed |
| Resolution | Fixed |
| Resolution Date | 2013-03-20T22:10:34.000+0000 |
| Affected Version/s | Alloy 0.3.4 |
| Fix Version/s | Alloy 1.1.0, 2013 Sprint 06 |
| Components | XML |
| Labels | Alloy |
| Reporter | Martin Broder |
| Assignee | Tony Lukasavage |
| Created | 2013-01-15T01:31:38.000+0000 |
| Updated | 2013-05-14T13:32:22.000+0000 |
Description
As described here: http://developer.appcelerator.com/question/146873/alloy-require-android-menu-not-possible
"In short, no, doesn't work right now for including Android Menus. The primary reason is that the Android Menu requires knowing what its parent node is in order to identify its containing Window, and in turn identify that Window's activity. This will be possible in Alloy, just not at the moment. The quick and dirty workaround is just to put your menu markup in the markup for the Window itself right now.
If you would be so kind, can you create a Titanium Community Jira ticket for this? That way I can get it prioritized and into my schedule ASAP. Be sure to give it the "alloy" label so it makes its way to me."
Resolved and augmented the following test app to show both explicit and required android menus in use: https://github.com/appcelerator/alloy/tree/master/test/apps/ui/android_menu
Now on tapping Android Menu, shows two options and both the menu options are working fine. Used the test app mentioned in the above link. Note - Observed that when options show, the label "Press the menu button" still shows in background. Tested in below environment - Appcelerator Studio: 3.1.1.201305132058 Titanium SDK: 3.1.1.v20130513131554 acs: 1.0.2 alloy: 1.1.2 npm: 1.2.14 titanium: 3.1.0 titanium-code-processor: 1.0.0 OS: Mac 10.8.2 Device: Samsung Galaxy Nexus (v4.0.4)