I am working for a client who owns the latest Tigra Menu Gold.
Anyway, they have dynamically built menus (from a struts action) with fixed width menus.
Occassionally, they will have menu items which are longer than the fixed width (plus font size) allows. As a result the text (quite nicely) flows onto a second line creating menu items which are 2 lines long, and look pretty good.
So far so good...
The problem is that although the menu item text flows over TWO lines, only the first line is recognized as selectable - actually the selectable area is the height of the menu items.
If you move the cursor over the first line of the two lines, everything if OK - cursor stays as hand pointer, menu stays showing, and the item is selectable. Unfortunately as you move the cursor over the second line of the 'flowed menu item' the cursor changes back to the default, the menu eventually times out, and you cannot select the item !!
Is this a bug ?
We can set the height for the menu items to be twice that of a single line (e.g. from 14 to 28), BUT then our single line entries end up taking up 2 lines of space and looking stupid. Is there no way to tell tigra menus to make the selectable area behind a menu item to be the full extent of the table cell behind it ?
The wrap of the text is more like a side effect, not feature. The size of the menu item specified in the configuration file must always be sufficient
for its content. ways around:
1. in your server side script estimate the size of the content by the length of the text and paddings, for the most accurate estimation with proportional fonts you may need to use character width lookup table. With the length known you can calculate the number of lines needed and print in height of the menu item ('sh' item scope setting)
2. request TMG 3.0beta in the support ticket, it supports automatic sizing
Thanks for the information... Any timeframe for when TMG 3.0 will be released ?
I don't want to use a beta product in a productoin environment - especially when 2.0 meets all of our requirements with no problems (apart fro the one identified).
Meanwhile, can you send the beta to my email address, or tell me how to 'open a ticket' on behalf of the client I am working for ?
Contact your client or person who's email was in the order form and ask for the support system login and password. You can also create own account, just make sure to specify the order ID in the ticket properties. We don't have the release date for v3.0, for most 2.6 performs just fine so we take extra time to test the code and save us from avalanche of the problem reports from thousands of users move to new version.