Recent Questions
Q: I am interested in your Deluxe Tree Menu. For testing purposes, i downloaded the trial version of your software, but realized that the Textboxes an comboboxes, as shown in the samples on your website, are not included in the demo version. As i am interested in right this feature, could you please tell me where i can find more information about how creating such input boxes in the css expanding menu, and maybe also if there is a possibility to change the menu and write the changed one into a database?
A: You are able to paste any html code within items.
For example:
var tmenuItems = [
...
["||<nobr><FORM method=GET action='http://www.google.com/custom'><input name='as_q'
value='searchthe web' size=15 style='font-size:10'> <INPUT type=hidden name=cof
value='LW:144;L:http://domain.edu/images/sulogo.gif;LH:45;AH:center;GL:0;S:
http://domain.edu;AWFID:e01cb67b8afe383e;'></form></nobr>","",
"images/icons/search.gif", "", "", "", "", "2", "", "", "",],
Try that.
Q: We have a problem with the submenus going cross-frame.
Whenever there is a webpage from another website in the content/target-frame the frameset twists and all the pages are shown in the topframe. A lot of the information on our web is in office word-files and when they are opened in the content/target-frame the same cross-frame-problem happens. Is it only possible for the sub-menus to go cross-frame when one of our own webpages is shown in the target-frame?
A: See more info about cross-frame mode here:
http://deluxe-menu.com/cross-frame-mode-sample.html
Notice, the menu will work correctly in the cross-frame mode if you load pages into the sub frame from the same domain.
If you load pages from another domain submenus won't be shown in the subframe - they will be shown in the frame with the top-menu.
It's caused by a security policy of browsers - a script can't modify a content of pages from another domain.
Q: Does your xml drop down menu support Arabic language fonts?
A: Actually you can use any letters in the menu.
Please, check that you've set "Tools/Use utf8 encode".
When you save your data file in UTF8 you should use the same encoding on our html page.
So you should write:
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
If you don't want to use UTF-8 encode on your page you should turn off
"Tools/Use utf8 encode" property, save your data file and manually
change your letters in any text editor.
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.