Recent Questions
Q: The contact page drop down menu examples would not work with the Firefox browser. And the submenu would show a white bg in the Internet Explorer browser.
A: Your color parameters are incorrect:
var itemBackColor=["91C24D","8B3A96"];
var itemBorderColor=["ffffff","ffffff"];
You should write them in the following way:
var itemBackColor=["#91C24D","#8B3A96"];
var itemBorderColor=["#ffffff","#ffffff"];
Q: Can a menu item that expands the submenu items when selected also work as a link?
A: Actually you cannot use links for the top items in the XP Style.
But you can write:
["<a href='index.html' class='home'>Home</a>","", "", "", "", "Return to Index page", "", "0", "", ],
["<a href='http://www.domain.uk' class='home'>About Us</a>","", "", "", "", "", "", "0", "", ],
["|Introduction","http://www.domain.uk/introduction.htm", "", "", "", "", "", "", "", ],
And create styles
.home{
color: #FFFFFF;}
.home:hover{
color: #FFBEBE;}
But in that case the submenu and link open when you press "About Us" item. I think that it is not verygood behaviour. You can also try to specify target parameter
["<a href='index.html' class='home'>Home</a>","", "", "", "", "Return to Index page", "", "0", "", ],
["<a href='http://www.domain.uk' class='home' target="_blank">About Us</a>","", "", "", "", "", "", "0", "", ],
["|Introduction","http://www.domain.uk/introduction.htm", "", "", "", "", "", "", "", ],
Q: I am currently using deluxe menu to generate a mouseover dropdown menu for my charity website - although it works fantastic in internet explorer it doesnt seem to work correctly in firefox, the mouseover dropdown menu looks flat and the special fade in effect doesnt work.
Please can you advise on what I am doing wrong.
A: Filters and transitional effects are features of Internet Explorer5.5+ only.
See more info here:
http://www.deluxe-menu.com/filters-and-effects-sample.html
Q: We are registered users of the Deluxe Menu software. Today I tried to use the Javascript API, but there is something I do not understand and want to ask for support.
First, I set up a very simple menu:
var menuItems=[
['Menu 1'],
['|Submenu 1'],
['Menu 2'],
['|Submenu 2'],
];
This menu is built via dm_init().
Then, I inspect the menu (in Firebug):
>>> dm_ext_getSubmenuParams(0, 0)
["dm0m0", 2, "", 0, 1]
>>> dm_ext_getSubmenuParams(0, 1)
["dm0m1", 1, "dm0m0i0", 1, 0]
>>> dm_ext_getSubmenuParams(0, 2)
["dm0m2", 1, "dm0m0i1", 1, 0]
Ok, there are three submenus. Now I am going to delete one of them:
>>> dm_ext_deleteItem(0, 0, 1)
"Menu 2" disappears on the screen, this works as expected. But now when I re-inspect the menu using the API, I find that the API reports exactly the same as before:
>>> dm_ext_getSubmenuParams(0, 0)
["dm0m0", 2, "", 0, 1]
>>> dm_ext_getSubmenuParams(0, 1)
["dm0m1", 1, "dm0m0i0", 1, 0]
>>> dm_ext_getSubmenuParams(0, 2)
["dm0m2", 1, "dm0m0i1", 1, 0]
So, it seems the report function continues to know about the original menu structure and reflects it. Am I using the API in a wrong way?
The problem I want to solve is to remove the entire menu dinamico dhtml, in order to rebuild it dynamically. Because I did not see a function aimed to this functionality, my plan was to delete all main menu entries subsequently until the main menu inspector no longer reports an entry. Is there (a better) way to achieve this?
A: Unfortunately, dm_ext_deleteItem() only change visibility of theseitems.
It doesn't delete them completely.
We'll try to fix it in the next versions of Deluxe Menu.