Recent Questions
Q: How do I make the top nav buttons exactly the same width for each button?
Total menu width is 743px and I have 6 buttons I want the width of each button to be fixed at 123px.
I set var menuWidth="743" but it averages out the buttons based on the text.
A: You should use individual item styles. For example:
var itemStyles = [
["itemWidth=123px"], //style 0
];
var menuItems = [
["Home","testlink.html", , , , , "0", , , ], //style 0
["Product Info","", "deluxe-menu.files/icon1.gif", "deluxe-menu.files/icon1o.gif", , , "0", , , ], //style 0
Q: For how long our purchase does entitle us to getting the upgrades for the dhtml menu software?
A: All minor upgrades you'll get for free (for example, 2.4->2.7).
All major upgrades you'll get for free during 1 year (for example, 2.4->3.0).
For example, if there's some major upgrades (1.7 -> 2.0 -> 4.0)
you'll get them for free during one year.
But if there'll be no major upgrades during some period (2.72 -> 2.81 -> 2.92). And after 3 year, for example, there will be major upgrade to 3.0. So you can upgrade for free.
We can offer you a big discount for the major upgrade after one year.
Q: I'm trying to set the frame parameters to frame name body. I have tried seven different text items: body, _body, frame name=body, framename=body, "framename=body", the relative URL, and the exact URL in the titemTarget parameter (common parameters). Nothing seems to work. It always sets the target to a new window. What text do I need to enter for the default parameter to be the body frame target?
Also, is there a way to expand only the menus and not the submenus? There doesn't seem to be a halfway point. Either all the menus are open, or all closed. If I set the default to hidden, it is non-functional. If I set it to expanded, that's not what I'm looking for either.
The menu looks good; other than these two problems it is functioning properly.
A: Please, check the following parameter:
var titemTarget="framename";
You can also set item target for each item
["|Home","testlink.htm", "default.files/icon1_s.gif", "default.files/icon1_so.gif", "", "Home Page Tip", "framename", "", "", ],
Try that.
> Also, is there a way to expand only the menus and not the submenus?
You want to expand only the main items when you load your page?
If it is so you can set expanded items by default.
If you want to expand specific items by default you should set "+"symbol at the beginning of item text.
["+Deluxe Tree: XP Style","", "default.files/xpicon1_s.gif", "", "", "XP Title Tip", "", "0", "", ], // this item is expanded by default
["|Home","testlink.htm", "default.files/icon1_s.gif", "default.files/icon1_so.gif", "", "Home Page Tip", "framename", "", "", ],
["|Product Info","", "default.files/icon2_s.gif",
"default.files/icon2_so.gif", "", "Product Info Tip", "", "", "", ], // this subitem is not expanded by default
Q: I'm trying to position my menus inside absolutely positioned <DIV> tags. If the <DIV> tag has style="position:absolute; top:100px; left:50px;" in the actual tag, deluxe-menu seems to work correctly. If I have the "position:absolute; top:100px; left:50px;" in a <STYLE> tag or a linked stylesheet and applied using id or class selectors, then deluxe-menu does not work correctly: sub menus have a 100pixel offset in the y direction and a 50 pixel offset in the x direction. This is with no change to the .js data file (I have absolutePos=0;) Is this a known issue, and is it planned to be fixed?
A: See, the problem is that the script can't get css properties of the object if they are described in separate .css block (or file).
In other words, you can't get the value of "position" attribute of the object if the object doesn't have this property within inline style(style="position:absolute"). To get the value you should move .css style into style="" attribute.
Please, try to add your
css file -> inline css, for example:
For example, you should add style="position:absolute;"
to the
<DIV id=head>
So, you'll have:
<DIV id=head style="position:absolute;">
Now we have only such solution for this problem.
We'll try to fix this problem in the future versions.