Recent Questions
Q: If you click a list drop menu link in the tree that opens a new page, for example, Solutions:By Type:Psuedo Wire , the link, Psuedo Wire, remains highlighted.
If you click a line that targets _self, for example, Solutions: By Type: T1 Extender, the link does not remain highlighted. My web app will need highlighting and all links will target _self. I have to solve this problem soon or else look elsewhere.
A: It is normal behaviour, your list drop menu can save its state within one page only.
You can try to use frames, and open pages in the content frame. Also you can use aserver-side script (php, asp, vb, etc.) to generate html pages fromtemplates on your server (we use this method on our website
http://deluxe-tree.com).
You should set a pressed item using Javascript API:
function apyt_ext_setPressedItem(menuInd, itemID)
<script type="text/javascript"><br>
var i = 4 //index of the selected item
onload=setPressed;
function setPressed()
{
dtreet_ext_setPressedItem(0,dtreet_ext_getItemIDByIndex(0, i));
}
</script>
To expand specific items you should use the following function: dtreet_ext_expandItem (dtreet_ext_getItemIDByIndex (0, 11), 1);
Q: I have problems with transitional effects with firefox
IE it’s ok but not in Firefox
Help me please
A: You cannot see transitional effects in Firefox because they arefeatures of Internet Explorer 5.5+ only.
See more info
http://www.deluxe-menu.com/filters-and-effects-sample.html
Q: I'm testing the trial version and I'm having a little problem with the state saving. Everytime it navigates to another page, it does not save the state, even with
var tsaveState=1;
In fact, it actually opens up a different menu other than the one I originally clicked.
A: See, if you open pages (with menus) from different folder it means that you open different menus. So, when you change a state, for example, of the first menu within "newzap/" folder and then open another page with the menu within "newzap/learn/", browsers looks for another cookie file and can't find it and the second menu stays in a default state.
Try to set different
var tsavePrefix="menu1";
var tsavePrefix="menu2";
var tsavePrefix="menu3";
for different menus.
That should work.
Q: Another problem I've found with v3.1 is that the top X value of the javascript floating menu is not used once you start scrolling a page.
A: Yes, we've made some changes in javascript floating menu feature in the new version.
Try to set
var floatable=2;