Recent Questions
Q: A lot of things have come in between... Just a few more Q's before I order.
1)
At the bottom of the page you refer to below, there is a table showing the tmenuItems array, itemInd and " submenuInd ". But in the examples on the same page, the function "dtreet_ext_getItemIDByIndex" takes the arguments (menuInd, itemInd). Is the argument "menuInd" the same as "submenuInd" referred to in the javascript menu design??
2)
When I highlight an item on "onload" I need to expand that item's parent(s), right? What will happen to other, already expanded nodes when I do that? Will they still be expanded or collapsed?
A: 1) menuInd is the index of a tree menu on a page, >= 0.
First menu - menuInd=0
Second menu - menuInd=1
Third menu - menuInd=2
Fourth menu - menuInd=3
...
2) Yes, the already expanded nodes will be expanded.
Q: We have two frames in a frameset, one for the menu and one for the content where the javascript menu frame expands normally without any problem. Our content frame's source is determined dynamically. The problem occurs when the content frame contains a page with another frameset in it. Unfortunately we can not avoid this for now. And when this happens our menu stops expanding.
A: Unfortunately it is really possible that you'll have problems in thatcase because the index of the content frame will be changed.
For example now you have:
<frameset id="frmSet">
<frame> //menu index=0
<frame> //content index=1
</frameset>
Your init function will be:
dm_initFrame("frmSet", 0, 1, 0);
But if you'll have frameset instead of content frame:
<frameset id="frmSet">
<frame> //menu index=0
<frameset>
<frame> // index=1
<frame> //content index=2
</frameset>
</frameset>
You should write your init function in the following way:
dm_initFrame("frmSet", 0, 2, 0);
You should change your javascript menu frame init function in that case.
Q: Deluxe Menu supports keyboard navigation eg. CTRL+F2 to activate menu.
Why does Deluxe Tabs not have the same feature?
I would like to use both java script navigation menu systems on the same page, and both need to have keyboard navigation for accessibility reasons.
A: Unfortunately it is really so, Deluxe Tree and Deluxe Tabs doesn'thave such a feature now.
We'll try to add this feature in the next versions of the java script navigation menu.
Q: I see "Incorrect Copyright" message in IE7.
A: Now you're using Deluxe Menu v1.12.
You should upgrade you Deluxe Menu to v2.0.
Please, download licensed files from the same link in your licensemessage.
How to upgrade to v2.00
---------------------------------------------------------------
You can download the licensed engine .js files from the same link in your license message. Deluxe Menu v2.00 has new parameters and features.
To upgrade to v2.00 you should do the following.
Step 1.
1.1 For Windows users
a. Run Deluxe Tuner v2.0
(can be found in the trial menu package v2.0
http://deluxe-menu.com/deluxe-menu.zip).
b. Open menu data file (.js file where menu parameters are placed):
select File/OpenA
c. Save the file: select File/Save, then click "No" button when the dialog box appears.
1.2 For other OS users
a. Open menu data file (.js file where menu parameters are placed) in a text editor.
b. Make sure that the following variables exist in the data file:
var keystrokes = 0;
var dm_focus = 1;
var dm_actKey = 113;
var dynamic = 0;
var smHideOnClick = 1;
var itemAlignTop = 'left';
var smSmartScroll = 1;
var dmAJAX = 0;
var dmAJAXCount = 30;
var dmRTL = 0;
var dmObjectsCheck = 0;
var menuBackRepeat = "repeat";
var menuHeight = "";
var transDuration2 = 200;
If one of the variables doesn't exist - add it at the beginning of the file.
c. Save the file.
Step 2. Now open HTML-page that contains Deluxe Menu.
Step 3. Replace existent tags of the menu by the following code:
<noscript><a href="http://deluxe-menu.com">Javascript Menu by Deluxe-Menu.com</a></noscript>
Step 4. Save HTML-page.
Step 5. New engine v2.00 has 7 .js files.
They are:
- dmenu.js
- dmenu4.js
- dmenu_add.js
- dmenu_dyn.js
- dmenu_key.js
- dmenu_cf.js (new v2.00)
- dmenu_popup.js (new v2.00)
Replace all old .js files by the files from v2.00.
Try that.