Recent Questions
Q: I have started using your menu and when testing in both IE-browsers the CPU jumps to 100% for at least 30 to 60sec.
Then the sub menu appears but also not as fast as in Firefox(no effects).
Now does my menu contains about 1476 item-lines, and I use the cross-frame modus.
Any ideas?
A: It is possible that the loading speed can be lower if the menu is very large. But it doesn't take so much time.
Yes, you can notice some delay in IE, but in over browsers it works better.
Deluxe Menu works fast, but 1500 is a large value.
I tried to create large menus on my machine: P4 3GHz, 512RAM WinXP SP2
It takes:
- 1000 items ~ 10 sec
- 2000 items ~ 40 sec
You can try to use AJAX-like technology.
http://deluxe-menu.com/ajax-technology-menu-sample.html
Q: Does the Deluxe menu work to load pages into an iframe?
(name=iframe1) I can't find any info on this ...
A: Of course. Please, use this parameter:
var itemTarget = "frame_name";
Q: We do need the menuitem separation bars as most of the menuitems are quit lengthy, and there needs to be a separation bar to distinguish between them.
A: If you want to add separators between items you can paste a separatorbetween items or you can set item's border width in the following way:
var itemBorderWidth="0 0 1 0";
But you cannot enter this value in Deluxe Tuner you should set thisparameter manually.
You can also create style for the last item with border width = 0:
var itemStyles = [
["itemBorderWidth=0"],
];
To add separators, please, see the following parameters:
//--- Separators
var separatorImage=""; //for subitems
var separatorWidth="5";
var separatorHeight="100%";
var separatorAlignment="right";
var separatorVImage="images/public/separator.gif"; //for the top items
var separatorVWidth="1";
var separatorVHeight="100%";
var separatorPadding="";
You should set a separator in the menuItems, for example:
var menuItems = [
["Home","index.cfm", , , , , , , , ],
["-"],
["About Us","about.cfm", , , , , , , , ],
];
Q: I appreciate your assistance with this problem. I am 98% of the way happy with this product. When I made the changes you suggested, the copyright error went away, however the site no longer validates. It does not like the <noscript> tags. Is there a fix for this?
A: Matt, you can move your <noscript> tag into the <body> tag.
Try that.