Recent Questions
Q: I can't get the hand pointer to work with my dhtml menu scripts in firefox and IE. I know that firefox requires the itemCursor to be set to pointer, but it doesn't work for all links in my menus. I believe that this worked in past version of deluxe-menu, but stopped working somewhere along the way. To recreate this, create a horizontal menu, and set the pressedItem to be one of the menu items and set the itemCursor to be "pointer". Then, you'll see that the pressed item's pointer is the finger icon, but the other menu items are just the arrow. Is there something I'm doing wrong or a setting that will fix this?
A: No, the reason is not in the pressed item.
See when you set:
var itemCursor="pointer";
your cursor will be a hand for the items with url only. For the itemswithout url it will be default arrow.
Q: Using the new version with unmodified menus results in a new frame menu indentation (the left border of the first javascript folding menu entries submenu in a frame menu setup is not aligned with its main menu entry (both in IE 6 and FF 1.5 / Linux)) - possibly we might need to arrange something?
A: I suppose that this is space to document borders. We've set this space, so that yoursubmenus will not look like the part of browser window. If you wantyou can delete that space.
Open dmenu.js file in any text editor and find the following code:
space=15;
Change 15 to 0.
space=0;
Try that.
Q: I would eventually like to be able to distribute the javascript navigation menu with some of my templates, is this permitted with the Developer license?
A: With the Developer license you can use the menu on an unlimited numberof Internet or Intranet sites and on the local machines.
This version of the script doesn't check keys and it isn't bound to a domain name,so it can be used with an application that doesn't have a fixed domain name.
Q: I'm testing the trial version and I'm having a little problem with the state saving. Everytime it navigates to another page, it does not save the state, even with
var tsaveState=1;
In fact, it actually opens up a different menu other than the one I originally clicked.
A: See, if you open pages (with menus) from different folder it means that you open different menus. So, when you change a state, for example, of the first menu within "newzap/" folder and then open another page with the menu within "newzap/learn/", browsers looks for another cookie file and can't find it and the second menu stays in a default state.
Try to set different
var tsavePrefix="menu1";
var tsavePrefix="menu2";
var tsavePrefix="menu3";
for different menus.
That should work.