Cmsmadesimple Dhtml Menu by Deluxe-Menu.com
Cmsmadesimple Dhtml Menu

Menu Screenshots

Cmsmadesimple Dhtml Menu Drop Down Men C Bc Java

Features

Easy Setup
  • De Luxe Tuner. GUI interface to create your cmsmadesimple dhtml menu menus easily and in no time
  • Sensible menu parameters for manual editing
Seamless Integration
  • Cross-frame support - menus work on frameset-based pages
  • Visible over flash, select boxes, iframes, java applets
  • Multiple menus on the same page
  • Amicable to other scripts and css styles
  • Any HTML code can be used inside menu items
How To Create Pull Down Menu In Html Cmsmadesimple Dhtml Menu
High Performance
  • AJAX menu loading - loads web menu data from the server "on-the-fly".
  • Commonly loads quicker than other html page elements
  • UL/LI items structure
  • Runs well with an unlimited number of submenus and items
Compatibility              
  • Full cross-browser compatibility including IE, Netscape, Mozilla, Opera, Firefox, Konqueror and Safari on Windows, Mac OS and Linux
  • Menu can be populated from a database using ASP, PHP, etc.
  • Search engine friendly
  • Support for any doctypes
  • Fits for secure sites
  • Section 508 compliant
Professional Look-n-feel
  • Entirely customizable look-n-feel
  • A lot of pre-designed cmsmadesimple dhtml menu samples
  • Hundreds of visual effects
  • Custom CSS styles can be applied for all menu settings



2.0 Buttons by Web-Buttons.com v3.0.0

Javascript Menu. DHTML Menu.

  • Good menu is an essential part of website commercial success. If people can't find their way around the site, they will fast give up seeking and retire, never to return. So, it's extreme serious that your website has a accurate, precise, prompt, and navigation of immaculate appearance.
    Don't let your web site guests to get lost. Try Deluxe Menu!

Recent Questions

Q: When I roll my mouse over my menu, it appears halfway down the page, not next to the menu. This only happens when I enclose the code in <div></div> layers. Is there a way to fix this?


A: It is possible that you have some problems with your css.

The problem is that the script can't get css properties of the object if they are described in separate .css block (or file).In other words, you can't get the value of "position" attribute of the object if the object doesn't have this property within inline style(style="position:absolute"). To get the value you should move .css style into style="" attribute.

Please, try to add your
css file -> inline css, for example:

You should add <DIV id=SiteMenu>

to the

style="position:absolute;"

So, you'll have:

<DIV id=SiteMenu style="position:absolute;">

Check that.


Q: For each item in my menu, can I specify an image in place of text or background?


A: If you want to use images instead item text, you should useindividual item styles. For example:

  var itemStyles = [
["itemWidth=200", "itemBackImage=image1.gif,image2.gif"], // style 0
["itemWidth=150", "itemBackImage=image3.gif,image4.gif"], // style 1
];

  var menuItems = [
[" ", "link", "", "", "tip", "target", "0"],
[" ", "link", "", "", "tip", "target", "1"],
];

Where "0", "1" - style number in itemStyles.

Please, use Deluxe Tuner application to create and assign individualstyles. You can find Deluxe Tuner in the trial package.


Q: A few of my users have reported issues with the menu like the one below. Where the drop down menu is just a white box with a little scroll bar in it. Can you please let me know how I might correct it or what is wrong? We are using version 2.4.


A: I've just checked your website. It works fine.

You can have such effect when the page entirely was not loaded yet. So, images were not loaded yet.

If you don't want to have such effect you can try not to use back images for the submenus.


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.