Recent Questions
Q: I was wonder if there was a way to have the css tree view already expanded with I open the page the menu is on instead of having to expanded every time.
A: The following parameter expands all menu items by default:
var texpanded=1;Q: Is this something I can adjust ...or make submenus were you can't see through them?
A: Try to set the following parameter:
var transparency=100;
Q: There seems to be a "glitch" when I use Firefox.
I have rebuilt the page twice but I always end up with themenu floating to the left, instead of under the main menu (the second or third mouseover will correct the issue). Also, sometimes I have to mouseover twice before the submenu comes up (in I.E.).
I have validated...however I wondered if there could be a conflict in the javascripting (yours and mine). Any suggestions?
A: The reason is in your <!DOCTYPE>.
Try to specify units in "px".
var menuWidth="780px";
var menuHeight="27px";
var smWidth="200px";
var smHeight="200px";
It's necessary to specify exact value for Mozilla browsers. It helpsto position menus correctly.
You can also try to set the following parameter:
var dm_writeAll=1;
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.