[
https://issues.apache.org/jira/browse/CLK-407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adrian A. resolved CLK-407.
---------------------------
Resolution: Won't Fix
Fix Version/s: (was: 2.4.0)
2.3.0
Issue is obsolete: the Menu control was already refactored a long time ago.
> Menu improvements - more properties: enable/disable, show/hide
> ---------------------------------------------------------------
>
> Key: CLK-407
> URL: https://issues.apache.org/jira/browse/CLK-407
> Project: Click
> Issue Type: Sub-task
> Components: extras
> Reporter: Demetrios Kyriakis
> Assignee: Adrian A.
> Fix For: 2.3.0
>
>
> Please improve the Menu Control, by allowing the user to show/hide menu
> items, and also to enable/disable them.
> Right now, this is not possible at all with the Menu Control :(.
> This is very limiting, making the existing Menu Control useless for most user
> applications, thus forcing the users
> to make their own menu controls (or the hack the original one).
> There's no need for these properties to be present in menu.xml, since their
> role is mostly at runtime:
> - enable/disable would allow to enable or disable a menu item (so to show it
> but make it unclickable).
> - show/hide would allow to to show and hide menu items (of course if the user
> doesn't have a specific role, the menu will be hidden).
> Regarding the API, it would be important to have practical methods for hiding
> and disabling menu items:
> something like Menu#hide(Menu item) would not be very practical since in most
> cases the "item" reference is not present
> so it should be Menu#hide(String path), and when applied, to seach this in
> the children items too.
> Another improvement would be if the Menu Click control would use Link
> Controls for the items (since that's what they are).
> Thank you,
> Demetrios.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
