Recent Questions
Q: The menu has a problem with newlines. The menu builds correctly (layout ok) but when pressed on the button nothing happens
At some point, in the DHTML menu, we have the following in the javascript:
var menuitems = [
["|Print HTML","javascript:alert('HTML print: Only the 7 most recent orders on the screen \n will be printed because of space limitations on paper.');printResult('4'); ","","", ,"_parent",,] ]
As you can see we have a newline (\n) between the words "screen" and "will". But when we click on the button nothing happens. If we remove the newline and we click on the button then we first get the alert box. After pressing the OK button the function printResult is called.
Is there any way for us to still use the newline character in the menuItems variable?
This can be easily reproducible. That's why I haven't made an example.
A: Try to write in the following way \\n:
["|Print HTML","javascript:alert('HTML print: Only the 7 most recent orders on the screen \\n will be printed because of space limitations on paper.');printResult('4'); ","","", ,"_parent",,]
Q: I downloaded the new version of dhtml menu source code copied the files over to my folder this menu was made with3.0 the files I copied over is 3.2 and now I get an error.
A: Now you have:
var fontStyle=["nirmal 12px Trebuchet MS, Tahoma","nirmal 12px Trebuchet MS, Tahoma"];
It is not correct. You should write:
var fontStyle=["normal 12px Trebuchet MS, Tahoma","normal 12px Trebuchet MS, Tahoma"];
Q: Your frameset FAQ/examples seem to tackle scenarios where submenus open in frame 2. I'm interested in in the actual menu selection opening in frame 2 (menus being in frame 1). Is there some documentation I've missed?
A: All info about installation of the menu in the cross-frame mode youcan find here:
http://deluxe-menu.com/cross-frame-mode-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.