Indexhibit Thickbox Leave Menu Visible by Deluxe-Menu.com
Indexhibit Thickbox Leave Menu Visible

Menu Screenshots

Indexhibit Thickbox Leave Menu Visible Dhtml And Hover Menu

Features

Cost Effective
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
Menu Bar Html Indexhibit Thickbox Leave Menu Visible
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
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
Easy Setup
  • De Luxe Tuner. GUI interface to create your indexhibit thickbox leave menu visible menus easily and in no time
  • Sensible menu parameters for manual editing



2.0 Buttons by Web-Buttons.com v3.0.0

Javascript Menu. DHTML Menu.

  • Use images for backgrounds of submenus and items, icons, arrows. Using web images you can create menus completely based on graphics.
  • Design both horizontal and vertical menus and submenus with any amount of menus on a single page.
  • Place any HTML code inside the menu item - be it a flash-object, form, picture, or text. This ability lets you to build various menus of any complexity.
  • Submenus can be shown in 4 ways: - From left to right and also from left to right + upwards. - From right to left and also from right to left + upwards (e.g. for right-to-left languages).

Recent Questions

Q: How can I load some text or a page into the javascript switch menu?

A: You should paste your content in the <div> .. </div> tags.

<div id="content1" style=" visibility: hidden;" class="tabPage">
<p align=center><img src="img/logo_DM.gif" width=262 height=56 alt="Deluxe-Menu.com"></p>
</div>

<div id="content2" style="visibility: hidden;" class="tabPage">
<p align=center><img src="img/logo_DT.gif" width=262 height=56 alt="Deluxe-Tree.com"></p>
</div>

<div id="content3" style=" visibility: hidden;" class="tabPage">
<p align=center><img src="img/logo_DTabs.gif" width=254 height=58 alt="Deluxe-Tabs.com"></p>
</div>

See in Deluxe Tabs there are two modes:

1.   var tabMode=0;
You can create only one level of tabs and assign Object Id's of the
DIV's to show when you click on the tab.

["XP Tab 1","content1", "", "", "", "", "", "", "", ],
["XP Tab 2","content2", "", "", "", "", "", "", "", ],
["XP Tab 3","content3", "", "", "", "", "", "", "", ],
["XP Tab 4","content4", "", "", "", "", "", "", "", ],

2.   var tabMode=1;
You can assign only links in this mode.
You should create top level items with subitems.

["XP Tab 1","", "", "", "", "", "", "", "", ],
 ["|Link 1_1","http://deluxe-tabs.com", "", "", "", "", "0", "", "", ],
 ["|Link 1_2","testlink.htm", "", "", "", "", "0", "", "", ],
 ["|Link 1_3","testlink.htm", "", "", "", "", "0", "", "", ],
 ["|Link 1_4","testlink.htm", "", "", "", "", "0", "", "", ],
 ["|Link 1_5","testlink.htm", "", "", "", "", "0", "", "", ],
["XP Tab 2","", "", "", "", "", "", "", "", ],
 ["|Link 2_1","testlink.htm", "", "", "", "", "0", "", "", ],
 ["|Link 2_2","testlink.htm", "", "", "", "", "0", "", "", ],
 ["|Link 2_3","testlink.htm", "", "", "", "", "0", "", "", ],
 ["|Link 2_4","testlink.htm", "", "", "", "", "0", "", "", ],
 ["|Link 2_5","testlink.htm", "", "", "", "", "0", "", "", ],
["XP Tab 3","", "", "", "", "", "", "", "", ],
 ["|Link 3_1","testlink.htm", "", "", "", "", "0", "", "", ],
 ["|Link 3_2","testlink.htm", "", "", "", "", "0", "", "", ],
 ["|Link 3_3","testlink.htm", "", "", "", "", "0", "", "", ],
 ["|Link 3_4","testlink.htm", "", "", "", "", "0", "", "", ],
 ["|Link 3_5","testlink.htm", "", "", "", "", "0", "", "", ],

You can use Object ID as well as Link in both modes. Use the following prefixes within item's link field:
"object:" - means that there is object id after it;
"link:" - means that there is a link after it.
"javascript:" - means that there is a javascript code after it, for example:javascript:alert(\'Hello!\')

So, you should write for example:
 ["|Link 1_1","object:Content1_1", "", "", "", "", "0", "", "", ],

Q: I set a custom target at '_mainFrame' required by Dreamweaver to view in a particular frame. When I click my button it opens in its own window.

Your thoughts would be appreciated.


A: Please, check the following code, for example
  var itemTarget="_mainFrame";

["Galerie de photos","photos/index.php", "img/arrow_r.gif","img/arrow_o.gif", , "_self", , , , ],

or

["Galerie de photos","photos/index.php", "img/arrow_r.gif","img/arrow_o.gif", , "_mainFrame", , , , ],

I suppose that now you have such code
["Galerie de photos","photos/index.php", "img/arrow_r.gif","img/arrow_o.gif", , "_blank", , , , ],


Q: When I click into a field and the calendar pops up that it doesn't pick up the date/time values.

I can display time in 12 or 24 hour format - however for the selection it only allows 24 hour format. My boss is yelling at me that it has to be in 12 hour selectable format.

A: > when I click into a field and the calendar pops up that it doesn't
> pick up the date/time values.
But you haven't specified hour in the date format. Now you have
%L %d, %Y, %l: %M %p
month day year abbreviated month name minute either `am' or `pm'
So, you have: January 29, 2009, Jan:54 am
See more info about conversion specifiers here:
http://calendardatepicker.com/parameters.html

> 2) I can display time in 12 or 24 hour format - however for the selection it
> only allows 24 hour format. My boss is yelling at me that it has to be in 12
> hour selectable format.

Try to specify date format in the following way:
%L %d, %Y, %l, %I:%M %p
So, you'll have: January 14, 2009, Jan, 03:50 pm


Q: It's simply not saving the state.  Clicking the items on the menu is inconsistent.  Sometimes it saves sometimes not.

  It seems to be a lot worse in this area.


A: See, Tree Menu saves it's state using cookies.
But it can't re-save the same cookie file from different folders.
For example, if the tree from "website/page.html" saves it's state,the menu from "website/content2/page.html" can't read this state andit creates it's own state. The problem is that it's a standardfeature of browsers and Javascript can't control that.