You can replace the default right-click menu of your browser with your own menu by using AllWebMenus DHTML menu maker!

Just be aware that this feature is supported by IE 5+, NS 6+ and Mozilla 1+ browsers only. In older browsers the default browser menu will appear instead.

To use this feature please follow the instructions below:

 

First, you should not forget to set the <Positioning> property to "Manually Trigger Groups as popup menus" before you compile the menu.

 

Compile the popup menu (eg: as popup_rightclick.js) and link it to your HTML page.

 

Open your web page(s) and include the following HTML code in the HEAD section (between the <head> and </head> tags):

<script>

function awmShowMenu(x,y,z,v){}

document.oncontextmenu = rightclickmenu;

function rightclickmenu(e) {

if (document.all) {awmShowMenu('popup_rightclick',event.clientX+

Math.max(document.body.scrollLeft,document.documentElement.scrollLeft),event.clientY+

Math.max(document.body.scrollTop,document.documentElement.scrollTop));}

else {awmShowMenu('popup_rightclick',e.pageX,e.pageY);}return false;}

</script>

 

 

Tags: , , ,

 

By using AllWebMenus you can use more than one DHTML menu on the same page if you compile and link these menus with different names.

Example:

1. Compile menu1.js and link it to the page

2. Compile menu2.js and link it to the page

Two menu-linking code sections will be created inside the html of the page. One for menu1.js and a different one for menu2.js (the order is not important).

How it works:

Let's say that you want to link a menu called "menu3.js" to a page. These are the actions taken place by AllWebMenus:

Does the menu-linking code already exist for "menu3.js"?

Yes Replace the old menu-linking code with the new one
No Insert a new menu-linking code for "menu3.js" into the page

Comments:

It is obvious from the above example that an additional menu will not be added in your page if its name already exists inside that page. So, you need to be careful not to use the same name for different menus even if they are located in different directories.

Multiple menus can take advantage of the "Tools -> Project Properties -> Compile Properties: Folders" capability so that common folders are used for the menu-building libraries and images (eg: awmdata).

You should not to use images with same names among different menus as they may override each other.

You can have as many menus as you like inside the same page but you should be careful not to over do it, as performance may be affected.

If the submenus of a menu overlap the other menu, you should change the <Z-Index> property in the menu that needs to be "in the background". Default value for this property is 1000; the "background" menu must have Z-Index value less than the value of the other menu (thus less than the default value).

 

Tags: , , ,

 

If you are one of the unfortunate cases that have lost the source file of your menu (i.e. the .awm file), we now come to the rescue!

Provided that you do have the compiled javascript menu file (menu.js) somewhere online or offline, we offer a "partial reconstruction" service to get the Menu Structure of your project into a new project file (.awm).

This is a manual process and costs $89, provided that the size of the menu is not too large.

Contact us if you wish to use this service.

Important Note:

This service recreates manually only the Menu Structure (the tree structure of items and groups), NOT the Style Properties. After you receive the reconstructed project from us, you will have to re-specify the style properties yourself to make your menu look as before.

Depending on your menu appearance (if you use customized styles for specific items or just the global Style Editor styles) you will gain about 80% of your time compared to re-designing the entire menu from scratch.

 

Tags: , , , , , , , ,

 

These are the new features and fixes introduced in version 5.1.736 (released on May 12, 2008):

- The <Link> property now supports unicode characters on the URL.

- The application now renders better on non-default DPI screen settings.

- All text-related properties can now be edited in larger forms.

- The default projects directory is the "My Documents" folder now instead of the "AllWebMenus\Examples" folder.

- Cross-frame implementations now also support the IE browser fix for the select boxes.

- All text-related properties can now be edited instantly on click (the"edit" button has been removed, as unnecessary step).

- The Server-Side Menus API Add-in fully supports the new enhancements of the <Border> property.

- Fixed a problem where the border property did not save all values on certain cases.

- The javascript libraries now fully support absolute positioned layers in HTML Text, when the "HTML - Full Mode / Ignore Style Properties" option is selected.

- Fixed a rare problem where the application ended unexpectedly in some cases.

- Fixed a problem where the images of the project did not show correctly in Preview Pane (but showed correctly live on the browser)

- Fixed a problem in Opera browser where the items looked wider than they should be.

 

 

Scripts generated by the AllWebMenus DHTML Menu Maker application create HTML <table> elements (and thus <tr> and <td> elements) in order to display the menu in your website.

Generic CSS rules that apply to all elements of a certain type (such as table) will also affect the elements created by the AllWebMenus' scripts. This can cause strange appearance of a menu.

Here is an example:

The original menu looks like this:

CSS rules like the following:

td {
text-align: center;
margin: 0.5em;
font-size: 100%;
color: black;
padding-left: 10px;
padding-right: 10px;
padding-top: 5px;
padding-bottom: 5px
}

and

tr { 
text-align: left;
 margin: auto;
 font-size: 100%; 
color: black;
padding-left: 10px; 
padding-right: 10px;
 padding-top: 5px;
 padding-bottom: 5px 
}

will cause a menu to look like this: menu broken by css in css example

Instead of the above rules, you can use classes and add these classes to the elements of the page you want the CSS rules to be applied:

td.TDdefinition {
 text-align: center;
 margin: 0.5em;
 font-size: 100%; 
color: black;
 padding-left: 10px;
 padding-right: 10px; 
padding-top: 5px; 
padding-bottom: 5px
 }

and

tr.TRdefinition { 
text-align: left;
 margin: auto;
 font-size: 100%; 
color: black;
 padding-left: 10px; 
padding-right: 10px;
 padding-top: 5px;
 padding-bottom: 5px 
}

and in the source code of your page you can use the following

<table …>

<tr class=”TDdefinition” …>

<td class=”TRdefinition” …>

...

</td>

</tr>

</table>

in the tables you want these CSS rules to be applied.

 

Tags: , , , , ,

 


© 2009-2013 Likno Blog – Drop-Down Menus, Javascript Menus, CSS Menus, jQuery Scrollers/Sliders, Modal Windows