Recent Questions
Q: I'm loving your product! It has definitely made my life easier.
I do have a question however. I know if I put a "+" in front of the title, the category will be expanded by default.
["+PRODUCTS","", "", "", "", "", "", "", "", ],
Is there a way to do that dynamically? Maybe have some code that would tell the sliding tree menu to expand on that particular page?
A: On your pages you should call the following function/functions to expand/highlight items, for example:
<script>
dtreet_ext_expandItem (dtreet_ext_getItemIDByIndex (0, 0), 1);
dtreet_ext_setPressedItem (0, dtreet_ext_getItemIDByIndex (0, 1));
</script>
See more info about API functions here:
http://www.deluxe-tree.com/functions-info.htmlQ: I am attempting to install a menu I've created into FrontPage2003.
I read what the web site says but it didn't seem to work. Any other suggestions?
A: Deluxe Menu wasn't developed as Dreamweaver/Frontpage extension,BUT you can use it as standard Javascript files. To install the menuinto your html page:
1. open the page in your program
2. open html source code of the page
3. add several rows of code (<script> tags), For info see: http://deluxe-menu.com/installation-info.html
That's all.
To create and configure your menus use Deluxe Tuner application
(included into the trial package): http://deluxe-menu.com/deluxe-tuner-info.html
Q: I was enthused to see you had cross-frame support for your menus. But, as I got into it, I discovered that your javascript transparent menu doesn't support frames within frames.
A: Actually Deluxe Menu works correctly with nested frames in most cases.Try to install Deluxe Menu in cross-frame mode. If you'll have someproblems you can send us a copy of your html page (including .js files) ora direct link to your website, so we can check it.
Q: I appreciate your assistance with this problem. I am 98% of the way happy with this product. When I made the changes you suggested, the copyright error went away, however the site no longer validates. It does not like the <noscript> tags. Is there a fix for this?
A: Matt, you can move your <noscript> tag into the <body> tag.
Try that.