Features

Easy Setup

De Luxe Tuner. GUI interface to create your expandable menu in indexhibit menus easily and in no time Sensible menu parameters for manual editing

Professional Look-n-feel

Entirely customizable look-n-feel A lot of pre-designed expandable menu in indexhibit samples Hundreds of visual effects Custom CSS styles can be applied for all menu settings

Web Navigation Expandable Menu In Indexhibit

Unrivalled Features

Scrollable, dragable, floating, right-click menus Keyboard navigation - press Ctrl+F2 to enter the menu Unique Java Script API for altering menu "on-the-fly", without page reloading AJAX technology - loads menu data from the server "on-fly and on-demand". Search feature - add the search area in the menu and type symbols. The found words will be higlighted. Sound support!

Seamless Integration

Cross-frame support - menus work on frameset-based pages Visible over flash, select boxes, iframes, java applets Multiple menus on the same page Amicable to other scripts and css styles Any HTML code can be used inside menu items

Cost Effective

Starts at just $39. Buy Now! FREE for non-commercial websites. Order Now! No-limits free trial version. Download Now!

2.0 Buttons by Web-Buttons.com v3.0.0

Recent Questions

Q: We're running deluxe_tree version 1.0. We are getting the following error:

_tsw is not defined
[Break on this error] String.prototype.sb=function(tss,te){return this.substring(tss,te)};String.proto...
dtree.js (line 14)

Any ideas? Should we upgrade to the latest version? If so, what it the upgrade path for us? Will we have to modify our data-tree.js file?


A: Yes, try to use Deluxe Tree v2.4.
See in Deluxe tree you should specify correct tWorkPath parameter:
<script type="text/javascript">  var tWorkPath="menudir/";</script> otn=tx/tl hre=T-"/ mt ae"ecito"cnet"nac orwbiewt it utn n e c

This parameter should point to the same folder with dtree.js file.When you use movable or floatable feature you should copy dtree_add.jsfile in the same folder with dtree.js file.
http://deluxe-tree.com/installation-info.html

Q: I used the drop menu creator to create a simple tab example, and I created a simple HTML file to display the tabs. It initially appears fine when the page first displays (e.g., the correct div is hidden), but when I *first* click on a tab I always get a javascript error deep in the .js code. Then I click around a bit between the tabs and get some display problems (no more javascript errors though), until finally the show/hide logic recovers and all looks ok.

The error I initially get is something like “tabs[…].id is not an object”. I have the IE7 debugger turned on, otherwise I might not ever see this error.

FYI, I tried your example menus on your web site and everything is fine! Maybe the .js files on your web site are not the same as those created by the generator?

A: You should set the following parameter in drop menu creator:

  var bselectedSmItem=0;

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: We are registered users of the Deluxe Menu software. Today I tried to use the Javascript API, but there is something I do not understand and want to ask for support.

First, I set up a very simple menu:

  var menuItems=[
['Menu 1'],
['|Submenu 1'],
['Menu 2'],
['|Submenu 2'],
];

This menu is built via dm_init().

Then, I inspect the menu (in Firebug):

>>> dm_ext_getSubmenuParams(0, 0)
["dm0m0", 2, "", 0, 1]
>>> dm_ext_getSubmenuParams(0, 1)
["dm0m1", 1, "dm0m0i0", 1, 0]
>>> dm_ext_getSubmenuParams(0, 2)
["dm0m2", 1, "dm0m0i1", 1, 0]

Ok, there are three submenus. Now I am going to delete one of them:

>>> dm_ext_deleteItem(0, 0, 1)

"Menu 2" disappears on the screen, this works as expected. But now when I re-inspect the menu using the API, I find that the API reports exactly the same as before:

>>> dm_ext_getSubmenuParams(0, 0)
["dm0m0", 2, "", 0, 1]
>>> dm_ext_getSubmenuParams(0, 1)
["dm0m1", 1, "dm0m0i0", 1, 0]
>>> dm_ext_getSubmenuParams(0, 2)
["dm0m2", 1, "dm0m0i1", 1, 0]

So, it seems the report function continues to know about the original menu structure and reflects it. Am I using the API in a wrong way?

The problem I want to solve is to remove the entire menu dinamico dhtml, in order to rebuild it dynamically. Because I did not see a function aimed to this functionality, my plan was to delete all main menu entries subsequently until the main menu inspector no longer reports an entry. Is there (a better) way to achieve this?

A: Unfortunately, dm_ext_deleteItem() only change visibility of theseitems.

It doesn't delete them completely.

We'll try to fix it in the next versions of Deluxe Menu.