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'm having trouble getting some of my drop down menu scripts opening in the frm2.
If you look under products, then Hard drives, then Rugged Airborne .....this one and Rugged Ground will not open in frm2 but the Contact Us and Get Quote are working fine.
Can you help me get these things to open in a frm2.
A: You should write your menu items correctly.
Now you have
["||Rugged Airborne","../RuggedAirborne.htm","Airborne,"frm2","0", ],
["||Rugged Ground","../RuggedGround.htm","Ground","frm2","0", ],
it is not correct.
You should write:
["||Rugged Airborne","../RuggedAirborne.htm","","","Airborne,"frm2","0", ],
["||Rugged Ground","../RuggedGround.htm","","","Ground","frm2","0", ],
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.
Q: Is it possible to open the dhtml tree to a particular state when a link is chosen from elsewhere in the site (not from a menu link)?
A: function dtreet_ext_expandItem (itemID, expand)
Expands/collapses a specified item or a submenu.
itemID - ID property of an item. expand - 0 - expand the item, 1 - show the item.
For example place to your HTML code
<script>
dtreet_ext_expandItem('dtree_0i2',0);
</script>
For details please see
http://deluxe-tree.com/functions-info.html