Recent Questions
Q: For any reason dropdown menu in javascript know shows incorrect accented characters.
A: You can save your data file in UTF-8 in Windows version of DeluxeTuner v3.2.7.
You should turn on "Tools/Use utf8 encode" property.
In that case your data file will be saved in UTF-8 encode.
Enter these symbols and save your data file.
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 manuallychange your letters in any text editor.
You can also replace your letters with special sets, for example
É - Capital E, acute accent - E
ç - Small c, cedilla - c
var menuItems = [
["É....","testlink.html", "", "", "", "", "", "", "", ],
["ç....","testlink.html", "", "", "", "", "", "", "", ],
Q: I still am having no luck with Firefox showing an Incorrect Copyright nag (Again, just Firefox for Mac; no problem with other browsers.)
Also, I am still requiring a long delay to keep the pop-up window open from loading as the page loads. Script reads:
deluxePopupWindow.attachToEvent(win,'openAfter=,,onClick=Image2,,,') }, 'load')
A: Delete 'openAfter=' at all from deluxePopupWindow.attachToEventfunction (in all files):
deluxePopupWindow.attachToEvent(win,',,onClick=Image2,,,')
deluxePopupWindow.attachToEvent(win,',,onClick=Image21,,,')
deluxePopupWindow.attachToEvent(win,',,onClick=Image22,,,')
deluxePopupWindow.attachToEvent(win,',,onClick=Image23,,,')
deluxePopupWindow.attachToEvent(win,',,onClick=Image24,,,')
In that case popup windows won't show till you click on the images.
You should write NOSCRIPT tag in the following way:
<noscript><a href="http://deluxepopupwindow.com">menu drop down by DeluxePopupWindow.com</a></noscript>
I've just checked it. There is no nag message in Firefox in that case.But notice that you won't have nag message on your website only. On alocal machine you'll have nag message.
Q: We have two frames in a frameset, one for the menu and one for the content where the javascript menu frame expands normally without any problem. Our content frame's source is determined dynamically. The problem occurs when the content frame contains a page with another frameset in it. Unfortunately we can not avoid this for now. And when this happens our menu stops expanding.
A: Unfortunately it is really possible that you'll have problems in thatcase because the index of the content frame will be changed.
For example now you have:
<frameset id="frmSet">
<frame> //menu index=0
<frame> //content index=1
</frameset>
Your init function will be:
dm_initFrame("frmSet", 0, 1, 0);
But if you'll have frameset instead of content frame:
<frameset id="frmSet">
<frame> //menu index=0
<frameset>
<frame> // index=1
<frame> //content index=2
</frameset>
</frameset>
You should write your init function in the following way:
dm_initFrame("frmSet", 0, 2, 0);
You should change your javascript menu frame init function in that case.
Q: Do you plan to implement a fix in the cross browser drop down menu for the pointer - many of our users have complained that it is very un-intuitive - surely it must be possible to change the pointer to a hand if there is a link. I have tried putting <a> tags in to the menu labels, but it only changes to a hand if the actual label text is highlighted - it obviously should change whichever part of the box is highlighted? Is there no other workaround?
A: If you set the following parameter:
var itemCursor="pointer";
You'll have the mousepointer being a hand for all itemsin the menu.
Unfortunately, you can't change cursor type for different items.
But you can write so:
["<a href='http://deluxe-menu.com/'>Home</a>","", , , , , , , , ],
["Product Info","", , , , , "0", , , ],
["|What's New","", , , , , "0", , , ],
In all items with links you should use <a> tag.
Set this parameter:
var itemCursor="default";