Recent Questions
Q: I can't get the popup menu sample (rightclick) to work in Opera. Does Deluxe-menu support opera for right-clicking?
Does Deluxe-menu have a gwt wrapper so we can use deluxe-menu as part of a GWT application?
A: Unfortunately, Opera doesn't support onContextMenu event.
More info you can find, for example, here:
http://lab.artlung.com/oncontextmenu/
Deluxe Menu wasn't developed as Google Web Toolkit extension,BUT you can use it as standard Javascript files.
To create and configure your menus use Deluxe Tuner application(included into the trial package):
http://deluxe-menu.com/deluxe-tuner-info.html
Please, try the trial version.
Q: I am a software developer interested in using deluxe menu for my company’s website. One of the important features of our website is multiple language support, typically Chinese.
Does deluxe menu have support for Chinese or other Unicode characters?
A: You're able to use any characters for Deluxe Menu in the same way asyou use them for standard html page.
The only issue is that submenus can be shown in incorrect positionwhen you're using dir=rtl for your page.
Please, try a trial version.
Q: Is there any way to change the font size of the secondary and tertiary links but yet have a different font size for the primary links?
A: You can use different font style for each link on each level.
You should use Individual Item Styles.
Please, use Dhtml Tuner application to create individual styles.
For example:
// --- DHTML Tuner style names ---
var tstylesNames=["Individual Style 1","Individual Style 2","Individual Style 3","Individual Style 4","New Individual Style",];
var tXPStylesNames=["Individual Style 1",];
var tstyles = [
["tfontStyle=bold 8pt Tahoma","titemBackColor=#265BCC,#265BCC","tfontColor=#FFFFFF,#428EFF","tfontDecoration=none,none"],
//style 0 ["tfontStyle=bold 8pt Tahoma","titemBackColor=#265BCC,#265BCC","tfontColor=#215DC6,#428EFF","tfontDecoration=none,none"],
//style 1 ["tfontDecoration=none,none"],
//style 2
["tfontStyle=normal 8pt Tahoma","tfontColor=#013D6D,#5555FF"],
//style 3
["tfontStyle=bold 11px Bookman Old Style","tfontColor=#000000,#000000","tfontDecoration=none,underline"],
//style 4
];
var tmenuItems = [
["+DHTML Menus","", "images/xpicon1.gif", , , "DHTML Menus", , "0", , , , ],
//style 0
["|DHTML Menu","http://dhtml-menu.com", "images/icon1.gif", "images/icon1o.gif", "images/icon1o.gif", "Information", "_self", , , , , ],
["|+DHTML Tree Menu","", "images/icon1.gif", "images/icon1o.gif", "images/icon1o.gif", "Support", "_self", "2", , , , ],
//style 2
["||2 styles: standard & XP","", , , , , , "3", , , , ],
//style 3
["|||Item 23","", , , , , , "4", , , , ],
//style 4
["|||Item 24","", , , , , , , , , , ],
["||Individual Item & Submenu Styles","", , , , , , "3", , , , ],
//style 3
["||Floatable & Movable Menu","", , , , , , "3", , , , ],
//style 3
....
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;