BTW This is a great menu and it is really simple to understand .. it must be .. I can understand most of it.
I am having a bit of loading trouble. It is really fast to load really, but then when you go from page to page the status bar reads "Closing mmenu.js" and this takes a long time sometimes, leaving a blank window until it sorts itself out.
Is there a way to load all the menus ( I have two on one page ) just one per session? So that it just loads...? All tyhe menu stuff is the same each page so it seems a waste of time to keep closing and opening the menus.
Any ideas?
Flash
Is there a wau to load the mmenu.js just once?
-
Flash_harry
- Advanced
- Posts: 11
- Joined: Wed Apr 23, 2003 4:30 pm
Hi Flash,
First the bad news. The menus are controlled with the javascript functions found in mmenu.js. As soon as you leave a page -- any page -- containing javascript, those functions are gone, along with the rest of the page. If menus are to be displayed on the next page, then the code that controls them must be available in that page. In other words, the code in mmenu.js must be loaded into any page where you want to use the menus. This is not a requirement specific to the menus; it's a requirement for any scripted functionality that is to act within a page... script can't run unless it's there!
The thing is, I've never heard of or seen this sort of behavior with Milonic menus. I've never even seen this message in a status bar (not to say it isn't there; I just have never seen it). I've looked at dozens and dozens of sites using this menu script and have never seen a page go blank and be slow to unload (at least not because of the menus). So I can't help wondering if it isn't related to something else. Are you able to post a URL so we can visit these pages and try to figure out what's going on? A test site perhaps?
Kevin
First the bad news. The menus are controlled with the javascript functions found in mmenu.js. As soon as you leave a page -- any page -- containing javascript, those functions are gone, along with the rest of the page. If menus are to be displayed on the next page, then the code that controls them must be available in that page. In other words, the code in mmenu.js must be loaded into any page where you want to use the menus. This is not a requirement specific to the menus; it's a requirement for any scripted functionality that is to act within a page... script can't run unless it's there!
The thing is, I've never heard of or seen this sort of behavior with Milonic menus. I've never even seen this message in a status bar (not to say it isn't there; I just have never seen it). I've looked at dozens and dozens of sites using this menu script and have never seen a page go blank and be slow to unload (at least not because of the menus). So I can't help wondering if it isn't related to something else. Are you able to post a URL so we can visit these pages and try to figure out what's going on? A test site perhaps?
Kevin
