Recent Questions
Q: I am working currently with deluxe-menu and am perfectly happy so far except one little thing: Does there exist a way to have the mousepointer being a hand instead of the regular pointer while going over the menu (like it would be regular links)?
A: You should set this parameter:
var itemCursor="pointer";
In this case you'll have the mousepointer being a hand for all itemsin the menu.
Unfortunately, you can't change cursor type for different items.
But you can write so:
["<a href='http://deluxe-menu.com/'>Home</a>","", , , , , , , , ],
["Product Info","", , , , , "0", , , ],
["|What's New","", , , , , "0", , , ],
In all items with links you should use <a> tag.
Set this parameter:
var itemCursor="default";
Q: Ok I found the problem. When I make var floatable=0; dhtml flyout menu stays perfectly on the top as before but when I change it to var floatable=1; then it stays on top when the page loads but moves down when the page fully loads.
A: There are additional parameters for floatable feature in v3.2 now.
You can find them in Deluxe Tuner.
Try to write:
var floatableDX=0;
var floatableDY=0;
These parameters set minimal space for widow border.
Q: When the html tab menu is initialized can you not have any selected tabs?
I do not want to select any tabs when the menu is initialized for some cases.
A: No, unfortunately it is not possible. Some top item should behighlighted.
But you can try to add separator in the beginning of the menu and set:
var bselectedItem=0;
var bseparatorWidth="0px";
var bmenuItems = [
["-",],
[" Deluxe Menu","content1", "img/icon_ie.gif", "img/icon_ie.gif", "img/icon_ie.gif", "", "", "", "", ],
[" Deluxe Tree","content2", "img/icon_ie.gif", "img/icon_ie.gif", "img/icon_ie.gif", "", "", "", "", ],
[" Deluxe Tabs","content3", "img/icon_ie.gif", "img/icon_ie.gif", "img/icon_ie.gif", "", "", "", "", ],
[" Contact us","content4", "img/icon_mail.gif", "img/icon_mail.gif", "img/icon_mail.gif", "", "", "", "", ],
];
Q: I've noticed something strange in the Deluxe Tree and I am wondering if this is normal.
Here's an example I have in my "data.js" file to populate the javascript ajax tree:
var tmenuItems = [
["Mes alertes/My alerts","", "", "", "", "", "", "0", "", "", ],
["|Francais","", "", "", "", "", "", "", "", "js/AjaxTreeFr.js", ],
["|English","", "", "", "", "", "", "", "", "js/AjaxTreeEn.js", ],
];
Here's basically how it goes:
- Basically the "0" represents a pre-built style that I have set for the root of my tree.
- Under this are the first child of the root called "Francais" and "English" which I link with a JS file to populate (Because the users will customize the alerts they want to see).
This works perfectly fine. But it is a workaround. Let me explain what I wanted in the first place:
var tmenuItems = [
["Mes alertes ","", "", "", "", "", "", "0", "", " js/AjaxTreeFr.js ", ],
["My alerts","", "", "", "", "", "", "", "", "js/AjaxTreeEn.js", ],
];
Basically I wanted to have 1 javascript ajax tree with 2 root items "Mes alertes" and "My alerts" but it seems impossible to attach a js file to the root of the tree view. (It doesn't get populated).
Any ideas?
A: See AJAX feature won't work for first-level in XP style now.
It works if you use:
var tXPStyle=0;