-
1. Re: 3.1.3 rich:dropDownMenu behaviour
mores Dec 21, 2007 12:09 PM (in response to mores)This illustrates the problem:
<rich:toolBar> <rich:menuItem value="Hover over me" /> </rich:toolBar>
I am using it this way because menuItem has an actionListener and dropDownMenu does not. -
2. Re: 3.1.3 rich:dropDownMenu behaviour
ilya_shaikovsky Dec 22, 2007 8:34 AM (in response to mores)you can't use menuItem inside anything except contextMenu and dropDownMenu components
-
3. Re: 3.1.3 rich:dropDownMenu behaviour
mores Dec 26, 2007 3:13 PM (in response to mores)Where is that documented ?
-
4. Re: 3.1.3 rich:dropDownMenu behaviour
ilya_shaikovsky Dec 27, 2007 7:25 AM (in response to mores)but where you have read that it allowed? ;)
Have you seen our demo? This components placed in the corresponding group not by chance. And the documentation on the DD menu and context menu says about these components usage while the documentation about toolBar doesn't describes such possibility.
But probably you're right.. We add a note to this components chapters that the components only designed to be used for Popup Menus lists construction.
Thanks! -
5. Re: 3.1.3 rich:dropDownMenu behaviour
mores Dec 27, 2007 8:21 AM (in response to mores)So if I need a non Drop Down menu bar, are you suggesting that I create one like the "List Shuttle" in the demo ?
Is it worthwhile to file an Enhancement on JIRA such that a toolBar can contain both DropDown items and menuItems ? -
6. Re: 3.1.3 rich:dropDownMenu behaviour
ilya_shaikovsky Dec 27, 2007 10:28 AM (in response to mores)Please.. explain me.. why you can't just use the example from listShuttle demo?
You may put any components to toolBar and call any actions using them -
7. Re: 3.1.3 rich:dropDownMenu behaviour
mores Dec 27, 2007 2:04 PM (in response to mores)I am currently creating a DropDown Menu Bar dynamically in code. The menu is populated from a database. Different people will have different security levels and therefore different menus.
If the user has permission to many items in 1 category I provide the DropDown functionality. If the user only has 1 menu in a different category I present that as a top level menu item.
My theory is why make a user drop down a menu if it only has 1 item.
( This did work in 3.1.2 and I liked the way it worked. ) -
8. Re: 3.1.3 rich:dropDownMenu behaviour
ilya_shaikovsky Dec 28, 2007 4:46 AM (in response to mores)ok.. so using conditional rendering - you may succesfully switch between DDMenu and simple command* in your toolBar.
-
9. Re: 3.1.3 rich:dropDownMenu behaviour
jbuechel Jan 11, 2008 11:08 AM (in response to mores)I'm facing exactly the same problem as mores described in the first post. And I am using rich:menuItem inside a rich:dropDownMenu component.
Please notice that I'm using event="onclick".
Here's the code:<rich:dropDownMenu event="onclick" value="#{messages.menu_online_directory}" rendered="#{s:hasRole('online_directory')}"> <rich:menuItem value="#{messages.menu_query_online_directory}" action="query_online_directory" /> </rich:dropDownMenu>
Will this be changed back to the old behavior or do I have to handle it by my self? -
10. Re: 3.1.3 rich:dropDownMenu behaviour
jbuechel Jan 16, 2008 8:21 AM (in response to mores)Will this behavior be changed back (as it was in 3.1.2.GA) for release 3.1.4.GA?
Would be great as i have to wait for 3.1.4.GA anyway due to "another regression bug" (RF-980).
I'd be happy about some information..
Thanks. -
12. Re: 3.1.3 rich:dropDownMenu behaviour
jbuechel Jan 17, 2008 8:27 AM (in response to mores)Thanks a lot!