Recent Questions
Q: What can I tell people who aren't seeing their drop-down menu? For example, I have a client who can't see his on his machine, while I can on see the menu on one of my machines but not the other.
Please advise what makes the difference and how to correct the problem.
A: When your security settings in IE doesn't allow Javascript onpages you load you can't see a dynamic page content. So, you cannotsee your javascript menu at all.
There is no way to enable these preferences automatically, in othercase there are no reasons to create security preferences.
You can use search engine friendly code, so you'll see all yourlinks (for the main items and submenus) when your security settings in IE doesn't allow Javascript.
You can generate search engine friendly code.
Deluxe Menu is a search engine friendly menu since v1.12.
To create a search engine friendly menu you should add additional html code within your html page:
<div id="dmlinks">
<a href="http://deluxe-menu.com">menu_item_text1</a>
<a href="http://deluxe-tree.com">menu_item_text2</a>
...etc.
</div>
To generate such a code use Deluxe Tuner application.
You can find this GUI in the trial package.
Run Tuner, load your menu and click Tools/Generate SE-friendly Code (F3).
Q: Shouldn’t the dhtml expand menu know what page you are on and expand accordingly?
Or would you need to ‘hard code’ each page to be expanded basedon that page?
A: You should set the following parameter
var ttoggleMode=1;
Deluxe Tree 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 dtreet_ext_setPressedItem (menuInd, itemID)
Please, see here:
http://deluxe-tree.com/functions-info.html
You can also set
var tsaveState = 1;
More info you can find
http://deluxe-tree.com/data-samples/tree-menuxp-save-state.htm
To expand specific items you should use API function
function dtreet_ext_expandItem (itemID, expand)
Try that.
Q: I am having some difficulty dynamically adding items to a dhtml sliding menus.
A: See dtreet_ext_insertItem () function has the following parameters:
function dtreet_ext_insertItem (menuInd, parentItemID, itemInd, itemParams)
Creates a new item and inserts it into a specified position.
menuInd - index of a menu on a page, >= 0.
parentItemID - ID property of an item.<, >= 0.
itemInd - index of a new item within the menu, >= 0.
itemParams - item parameters.
Notice that parentItemID is the Id property of the parent item
(notindex). If you want to add top items you should set parentItemID=0.
itemInd - you should use this parameter if you want to add item in the
specific place, for example set itemInd=5 if you want to add item
before the existing item with itemInd=5.
If you set itemInd=null the new item will be added at the end of this submenu and its index will be added automatically.
Q: I'm trying to position my menus inside absolutely positioned <DIV> tags. If the <DIV> tag has style="position:absolute; top:100px; left:50px;" in the actual tag, deluxe-menu seems to work correctly. If I have the "position:absolute; top:100px; left:50px;" in a <STYLE> tag or a linked stylesheet and applied using id or class selectors, then deluxe-menu does not work correctly: sub menus have a 100pixel offset in the y direction and a 50 pixel offset in the x direction. This is with no change to the .js data file (I have absolutePos=0;) Is this a known issue, and is it planned to be fixed?
A: See, the problem is that the script can't get css properties of the object if they are described in separate .css block (or file).
In other words, you can't get the value of "position" attribute of the object if the object doesn't have this property within inline style(style="position:absolute"). To get the value you should move .css style into style="" attribute.
Please, try to add your
css file -> inline css, for example:
For example, you should add style="position:absolute;"
to the
<DIV id=head>
So, you'll have:
<DIV id=head style="position:absolute;">
Now we have only such solution for this problem.
We'll try to fix this problem in the future versions.