I've been experimenting with the 3.5 Menu builder for a couple days and have completed a working set of menus to replace what I use on my web site today.  But in trying the various browsers I normally test with I ran into a problem loading the menus in NV4.04.  I get the error:

function LoadMenus() {if(!rjsPath){window.setTimeout("LoadMenus()", 10);return false;}document.write('<' + 'script language="JavaScript" type="text/javascript" src="' + rjsPath + 'menu.js"><\/script>');}LoadMenus();

on the paranthesis preceding the LoadMenus()
with the text:
function does not always return a value.

Any suggestions on what this is related to?

Another thing I noticed is that when using NV 4.04 to view another site that uses this same package, NV 4 does not display this page at all correct and if I try to click on a link on one of the menu items, it crashed NV and locks up my computer...reboot.  I'm using Windows 98.

So right now, I'm thinking this package and NV 4 just don't get along at all.  Yet I thought this was suppose to work with NV4.  Is there a minimum revision level that must be used?

I will fix the problem with the new loader code for the next release.

You will not have this problem if you compile your project using a non-relative configuration.

--------

It’s so easy to crash Navigator 4 that almost anything could cause it to fail, especially if the site you tested had a complex design (many tables, CSS declarations, large pieces of javascript code, etc...)

I'm no longer testing the menus created with DMB under so old versions of Navigator 4, but if you encounter any problem(s) with your own menus you just have to post it here and I'll try to modify the code to avoid Navigator 4 from crashing.

compile your project using a non-relative configuration?

Can you be more specific?  I assume you are referring to modifying some of the check boxes under the Global Settings Tab in Project Properties?  I have the first 3 checked, Nav4 clip bug fix, and Hide Form Elements.

Right now, my own menus don't crash Nav 4.  But it could just be it doesn't get far enough because it can't load them yet.  So if I can get past this first problem, we'll see what happens next.  

I know that Nav 4 is old, but there are still folks out there using it, and if they can't get the menus to work, the web site is redendered useless for that visitor.   This is simply unacceptable.  What may be needed is a Nav 4 switch that falls back to a braindead text menu.   In other words, allow us to turn on an alternate presentation that doesn't challenge Nav 4.

Note that DMB's menus will work just fine under Navigator 4. I didn't mean to say that I'm not supporting this browser.

What I meant to say is that I prefer to concentrate on versions such as 4.78 which are more popular among users than any other previous releases.

--------

DHTML Menu Builder supports three types of configurations:

1) Relative (the default one).
2) Local
3) Remote

You can create additional configurations through the File->Project Properties->Configurations dialog.

--------

I recommend you not to worry too much about this issue.
Version 3.6 will be released soon and I've tweaked to code to conform to the bogus implementation of the javascript parser from older Navigator 4 releases.

And if you wish you can apply the fix your self.
Just change your current code from this:

to this:

That cleared up all the problems...thank you.  My menus now work great on IE6, NV4.04, NV6, and Opera 6.  I appreciate the great support and quick response!  

I look forward to the next release, and in the meantime, I can keep making progress on getting all the menus done.

Great!
Thanks for letting me know.

Hopefully, the next version will be released in just a couple of days.