Milonic provide full featured pull down web menus for some of the worlds largest companies
click here to see what it can do for you

Download Milonic DHTML Menu
Buy Milonic DHTML Menu

Back To Start Of Archive
Taken From The Forum: Archived Topics for the old Version 3.0 JavaScript Menu
Forum Topic: Click to view post
Last Updated: Thursday February 8 2018 - 06:02:35

I am Sure this is a very simple Frame problem - !!

Poster: crawley
Dated: Wednesday December 11 2002 - 13:40:38 GMT

I have done this so many times but this time I have obvioussly cocked up somewhere but can't see where.

Here's my url the only sub part of the menu I've set up is under 'Advertise' but it doesn't show in the frame - It may be showing behind the frame - it was for a time. The menu arrays are menuh_array.js (header)(in the html directory) and menub_array.js (body)

Any clues?

Poster: trytrix
Dated: Wednesday December 11 2002 - 18:46:44 GMT

Hi Crawley,

I went to your URL.

This is what I see using Netscape7 :
This is what I see using IExplorer 6 :

Both the same and not showing much !!

Your code isn't very readable !

Normally the content of the site visited is being cached locally on the hard disk under "..\Temporary Internet Files\Content.IE5" (when using IE).
But .. not in this case !!
So I could'nt have a look at your "menu*.js" files.

Had a quick view at your html source code. Some suggestions..
It's better to put your menu*.js files immediately after the <body> tag.
You could use a baseUrl variable definition to extend the path-definition.

Maybe Kevin has some better explicable reason ?


Hi this was only a test which is why it isn#t really there!

Poster: crawley
Dated: Wednesday December 11 2002 - 19:05:15 GMT

didn't you look at the menu arrays? and the reason why the script is at the bottom is I tried it everywhere else and it didn't change a thing. Can anyone help?

Poster: kevin3442
Dated: Thursday December 12 2002 - 5:34:59 GMT

Hi Sharon,

I have a few observations that might help:

(1) You've left out the following global parameters, used for implementing the menus across frames. The menu will not show in the main frame without these.

Frames_Top_Offset=0 // Frames Page Adjustment for Top
Frames_Left_Offset=-36 // Frames Page Adjustment for Left

These values are normally found with the other globals at the top of an x_array.js file (e.g., timegap, followspeed, etc.). The values shown are from the frames example on the Milonic website. You'll probably want to keep the top offset at 0, but adjust the left offset to a value (probably a positive one in your case) that works for your own site. Most people put these in the array files for both frames, using identical values in both. I've found, however, that they seem to be important only in the frame containing the calling menu (i.e., the main menu); but just to be safe...

(2) Your menub_array.js file contains the following:

Code: Select all

,"Modify Listing","modifylisting.html",,,0

(comments removed to prevent wrapping)

The "body" menu array was started, but it only contains menu properties, no actual menu items; and the array is not closed before a new menu is added. The "advertise" menu array is added, but only with items defined... no general properties (e.g., width, border width, style array, etc.) It's almost like the whole thing was intended to be one menu??? This'll have to be fixed, or it'll certainly cause strange things to happen!

Some general points...

(3) You'll probably want to take the "advertise" menu array out of the menuh_array.js file (I guess you probably put it there during your testing).

(4) With frames, version 3.5.10 of mmenu.js leaves the Mouse On Background color turned on in a main menu selection that opens a submenu, even after the submenu closes. This may not be a concern to you, since you seem to alter only the font color, not the background color, for mouseovers (font color is unaffected). Just thought you should know this, in case you later decide that you want to add background color changes to your mouseover effects. Version 3.5.05 is the most recent one I know of that doesn't suffer from this issue.

(5) I noticed that your top frame doesn't have a name. No big deal now, since your header file doesn't have any functions or variables that you want to access, but it might be handy to have down the road.

Hope that helps,