Spry Menu For Dreamweaver Rapidshare by Deluxe-Menu.com
Spry Menu For Dreamweaver Rapidshare

Menu Screenshots

Spry Menu For Dreamweaver Rapidshare Tutorial Popup Menu

Features

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
Unrivalled Features
  • Scrollable, dragable, floating, right-click menus
  • Keyboard navigation - press Ctrl+F2 to enter the menu
  • Unique Java Script API for altering menu "on-the-fly", without page reloading
  • AJAX technology - loads menu data from the server "on-fly and on-demand".
  • Search feature - add the search area in the menu and type symbols. The found words will be higlighted.
  • Sound support!
Dhtml Drop Down Layer Spry Menu For Dreamweaver Rapidshare
Easy Setup
  • De Luxe Tuner. GUI interface to create your spry menu for dreamweaver rapidshare menus easily and in no time
  • Sensible menu parameters for manual editing
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
Cost Effective



2.0 Buttons by Web-Buttons.com v3.0.0

Javascript Menu. DHTML Menu.

  • Good navigation is an important step to website success. If people can't find their way around the site, they will quickly give up looking and leave, never to return. So, it's absolute vital that your website has a fast, neat, and eye-pleasing navigation.
    Don't allow your website visitors to get lost. Try Deluxe Menu!

Recent Questions

Q: We are using a licenced version of your tree-menu.
Now we have a situation, where we should show the actualclicked menu position with an icon or a color for a collapse tree menu.

A: This can be found with the help of external function of tree menu.
dtreet_ext_userClick(itID, event) - this function is called when clicking a mouse button on the item.

itID - item id
event - standard structure of events generated browser
dtreet_ext_getItemParams (menuInd, itemID) - returns all item parameters.

Please visit http://deluxe-tree.com/functions-info.html for addition information.


Q: My top levels over the menu have no link and as such I need the cursor not to change when hovering over it – only change over the menus that drop down.

Please let me know how to fix this


A: Unfortunately, you can't change cursor type for different items.
But you can write so:

["< a href='http://deluxe-menu.com/'> Home ["Product Info","", , , , , "0", , , ],
 ["|What's New","", , , , , "0", , , ],

In all items with links you should use < a> tag.

Set this parameter:
  var itemCursor="default";


Q: We have purchased 'Deluxe Menu...'.
We are integrating the menu into the site. However, we are facing an issue i.e. drop down menu with css overlapping the 'Select' box in the IE 6.0.

I went through the help pages in the deluxe menu website and tried out the Suggestion of assigning 1 to dmObjectsCheck i.e.   var dmObjectsCheck=1 and adding the function as below.

function dm_ext_ruleObjectHide()
{
return !document.all;
}

It is throwing some error when we do that. Could you please suggest, what should we to get rid of overlapping. Please see the attached screen for the error. The error captured using Firefox.

A: Check that you're using Deluxe Menu v3.2.5.
Check also that you have dmenu_add.js file in the same folder withdmenu.js file.

Or you can try to set also the following parameter:

  var useIFRAME=1;



Q: When I run the cursor over the menu, the menu images disappear for usually a split second, but sometimes for several seconds at a time. Is there a way to make the image static or keep it solid when the cursor runs over it?


A: You can have such effect when the page entirely was not loaded yet.
So, images were loaded only for the 1 state and for the other stat were not loaded yet.

If you don't want to have such effect you can use 1 state buttons.