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: I activated option "state saving" but I think there's a problem;
when I open the website and click on an item of the menu, the pressed item becomes red
(up to now it's ok), but if I have topress F5 on the keyboard or press on the refresh button
to refresh the web page, the pressed item loses its color red.
I'd like the pressed item in the dhtml expand menu to maintain its color after the refresh command.
How can I solve this problem?
A: Tree Menu doesn't save a presseditem as it saves a tree state.
It works within 1 page only and if youreload the page you should set a pressed item using Javascript API:
function apyt_ext_setPressedItem(menuInd, itemID)
<script type="text/javascript">
var i = 4 //index of the selected item
onload=setPressed;
function setPressed()
{
dtreet_ext_setPressedItem(0,dtreet_ext_getItemIDByIndex(0, i));
}
</script>
Q: I know. I have two menus on the page and I am not using beforeItemImage orafterItemImage for the top menu in javascript (the one you referenced below), but I need it for the second menu. The parameters for that menu are in mainnav_data.js.
Even when I only call dmWorkPath and dmenu.js once, it does not work.
A: See, it is not correctly to use image-based items:
["","", "mainnav_data.files/corpinfo.gif", "mainnav_data.files/corpinfo2.gif", "", "_self", "0", "", "", "", "", ],
and specify beforeItemImage/afterItemImage parameters. They won't work in that case.
You can create such buttons in the following ways:
1) Use image-based menu (images with text).
Create normal and mouse-over state images (with text) for each item:
["","", "mainnav_data.files/corpinfo.gif", "mainnav_data.files/corpinfo2.gif", "", "_self", "", "", "", "", "", ],
["","", "mainnav_data.files/new.gif", "mainnav_data.files/new2.gif", "", "_self", "", "", "", "", "", ],
["","", "mainnav_data.files/xxxxx.gif", "mainnav_data.files/xxxxx2.gif", "", "_self", "", "", "", "", "", ],
2) Use combined background for the menu in javascript items (images without text).
var beforeItemImage = [,]; //left-side image for normal and mouse over state
var itemBackImage = [,]; //background or image for normal and mouse over state
var afterItemImage = [,]; //right-side image for normal and mouse over state
var beforeItemImageW = '';
var afterItemImageW = '';
var beforeItemImageH = '';
var afterItemImageH ='';
But you should create a small images in any Graph Editor, for example:
button_n_back.gif
button_n_left.gif
button_n_right.gif
button_o_back.gif
button_o_left.gif
button_o_right.gif
You cannot use these two methods together!
Q: How does the search engine stuff work. A web developer told me to stay away from java script if you want google to recognize your webpage.
Can you comfort me by telling me how it works.
A: Spiders can't read dynamically-generated Javascript code, so theycan't read menu links.
Search engine friendly means that you can add additional html codewithin your html page. You can generate such a code using Deluxe TunerGUI that you can find in the trial menu package. But if you'll use themenu without any additional html code, spider won't see menu links.