Recent Questions
Q: Trying to install XP style floating dhtml slide down menu but have these problems:
- Menu does not stay within table cell
- Is not floating
A: > - DHTML slide down menu does not stay within table cell
You're using the floating feature now. Your dhtml slide down menu will float withabsolute position only. So, now you have:
var tabsolute=1;
var tleft="1px";
var ttop="1px";
That is why your dhtml slide down menu does not stay within table cell and hasabsolute position.
> - Is not floating
Try to call on your page
<script type="text/javascript" src="philmenu.files/dtree_add.js"></script>
Q: Hi There. I wanted to use your product, but couldn’t figure out how multiple users could get varying menus using the file driven approach.
I currently use a java menu that I build on the fly without any files.
The only thing I could come up with was having each user refer to his/her own data.js file, that I can build on demand.
Does that make sense to you?
A: Deluxe Menu is Javascript code only. It requires several .js files andit's generated on a client side.
Theoretically it is possible to have varying menus for multiple users.You should create your own server-side script (for example, php) thatwill change the menu for your users. The menu doesn't support such afeature.
Q: I just purchased your Deluxe Menu maker. Wonderful tool!
I have made a menu, uploaded it to my HTML folder at Typepad in the correct place and tried several OTHER places too.
I have inserted the js snips into the head and body in all permutations of combinations.
I checked it each time by both opening my site and viewing source.
The menu is there. But it cannot be seen on the page. Never has been seen. Not even a hint of it being there.
I tried .js .file AND .js AND CSS.
No menu.
I checked on four browsers.
No menu.
I verified the files are in my index place by copying them to notebook.
I have done all of the above about 20 times EACH.
A: See, now you have:
<title>The Steel Deal - an oasis of reason in a sea of insanity.</title>
<!-- Deluxe Menu -->
<noscript><a href="http://deluxe-menu.com">Javascript Menu by Deluxe-Menu.com</a></noscript>
<script type="text/javascript"> var dmWorkPath = "/";</script>
<script type="text/javascript" src="dmenu.js"></script>
<!-- (c) 2007, by Deluxe-Menu.com -->
....
<meta name="verify-v1" content="VP25uY4F2NriQQhn7R3wK4aeYoMZpbafF+kkwx+vze4=" />
<!-- Deluxe Menu -->
<noscript><a href="http://deluxe-menu.com">Javascript Menu by Deluxe-Menu.com</a></noscript>
<script type="text/javascript"> var dmWorkPath = "/";</script>
<script type="text/javascript" src="/dmenu.js"></script>
<!-- (c) 2007, by Deluxe-Menu.com -->
</head>
It is not correct. You should call dmenu.js file only once.
Please, delete the second code.
There is now engine .js files
dmenu.js
dmenu4.js
dmenu_add.js
dmenu_dyn.js
dmenu_key.js
dmenu_cf.js
dmenu_popup.js
dmenu_ajax.js
and data file on your server.
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.