<HTML>I'm asking because of that ColdFusion wrapper I wrote. Am about to plug it into more sites I'm building, and release an upgrade of a commercial product I sell with a fancier version of that wrapper inside (with the recommendation to d/l, use and pay for your menu, of course ;D).
The public version of that CF menu wrapper is probably going to cross 200 downloads in a day or two. Its still on the front page of the Macromedia ColdFusion Developers Exchange.
Cheers,
--Matt--</HTML>
Will mmenus.js in 3.3 be 3.2-compatible?
-
matt@mysecretbase.com
- Beginner
- Posts: 8
- Joined: Sun May 19, 2002 7:23 pm
-
matt@mysecretbase.com
- Beginner
- Posts: 8
- Joined: Sun May 19, 2002 7:23 pm
Re: Will mmenus.js in 3.3 be 3.2-compatible?
<HTML>Gotcha. Thanks!
Given the nature of Macromedia's update cycle (they can disappear for weeks), I'll probably wait until I absolutely must to update the tag.
Cheers,
--Matt--</HTML>
Given the nature of Macromedia's update cycle (they can disappear for weeks), I'll probably wait until I absolutely must to update the tag.
Cheers,
--Matt--</HTML>
-
dennis__hansen@hotmail.co
- Beginner
- Posts: 7
- Joined: Sun May 19, 2002 7:23 pm
Re: Will mmenus.js in 3.3 be 3.2-compatible?
<HTML>> , // ID of the div you want to hide on MouseOver (useful for hiding form
> elements)
Just wanted to say that I'm looking forward to this feature !
It's not active in the online beta version is it ?
see..I can't wait
Dennis</HTML>
> elements)
Just wanted to say that I'm looking forward to this feature !
It's not active in the online beta version is it ?
see..I can't wait
Dennis</HTML>
-
Guest
Re: Will mmenus.js in 3.3 be 3.2-compatible?
<HTML>There is one very slight change to one of the variables.
The structure is the same however, so it wont affect your plug-in.
If I remember correctly I've changed what one of the variables in the menu array represents heres a sample
addmenu(menu=[ // This is the array that contains your menu properties and details
"mainmenu", // Menu Name - This is needed in order for the menu to be called
95, // Menu Top - The Top position of the menu in pixels
10, // Menu Left - The Left position of the menu in pixels
, // Menu Width - Menus width in pixels
3, // Menu Border Width
, // Screen Position - here you can use "center;left;right;middle;top;bottom" or a combination of "center:middle"
style1, // Properties Array - this is set higher up, as above
1, // Always Visible - allows the menu item to be visible at all time
, // Alignment - sets the menu elements text alignment, values valid here are: left, right or center
, // Filter - Text variable for setting transitional effects on menu activation - see above for more info
, // Follow Scrolling - Tells the menu item to follow the user down the screen (visible at all times)
1, // Horizontal Menu - Tells the menu to become horizontal instead of top to bottom style
, // Keep Alive - Keeps the menu visible until the user moves over another menu or clicks elsewhere on the page
, // Position of TOP sub image left:center:right
, // Type of menu use "form" or blank
, // Right To Left - Used in Hebrew for example.
, // Open the Menus OnClick - leave blank for OnMouseover
, // ID of the div you want to hide on MouseOver (useful for hiding form elements)
, // Reserved for future use
, // Reserved for future use
, // Reserved for future use
,"Home","/menu/",,,3// "Description Text", "URL", "Alternate URL", "Status", "Separator Bar"</HTML>
The structure is the same however, so it wont affect your plug-in.
If I remember correctly I've changed what one of the variables in the menu array represents heres a sample
addmenu(menu=[ // This is the array that contains your menu properties and details
"mainmenu", // Menu Name - This is needed in order for the menu to be called
95, // Menu Top - The Top position of the menu in pixels
10, // Menu Left - The Left position of the menu in pixels
, // Menu Width - Menus width in pixels
3, // Menu Border Width
, // Screen Position - here you can use "center;left;right;middle;top;bottom" or a combination of "center:middle"
style1, // Properties Array - this is set higher up, as above
1, // Always Visible - allows the menu item to be visible at all time
, // Alignment - sets the menu elements text alignment, values valid here are: left, right or center
, // Filter - Text variable for setting transitional effects on menu activation - see above for more info
, // Follow Scrolling - Tells the menu item to follow the user down the screen (visible at all times)
1, // Horizontal Menu - Tells the menu to become horizontal instead of top to bottom style
, // Keep Alive - Keeps the menu visible until the user moves over another menu or clicks elsewhere on the page
, // Position of TOP sub image left:center:right
, // Type of menu use "form" or blank
, // Right To Left - Used in Hebrew for example.
, // Open the Menus OnClick - leave blank for OnMouseover
, // ID of the div you want to hide on MouseOver (useful for hiding form elements)
, // Reserved for future use
, // Reserved for future use
, // Reserved for future use
,"Home","/menu/",,,3// "Description Text", "URL", "Alternate URL", "Status", "Separator Bar"</HTML>
-
Guest
Re: Will mmenus.js in 3.3 be 3.2-compatible?
<HTML>Forgot to answer your question.
Yes they will be compatible.
-- Andy</HTML>
Yes they will be compatible.
-- Andy</HTML>