If you could send me the sample of code or, even better, the url to the site, we might look in to it a bit.
It is now necessary for me to change the menu system a bit and I've incorporated new menus using a Dreamweaver extension that plugs in all the scripting.
I wonder if the extension you're using is Helmi DHTML extension? If that's the case you might want to update the libraries used in your site in to version delivered with Helmi DHTML extension. That's because Helmi has a slightly modified version of DynAPI 2.5.7 (we have fixed few bugs there).
To do that you may either use Helmi's automatic update function to update the local set of libraries (remember to delete the old libraries from your current site and add some DynAPI objects from Helmi meno so that Helmi writes the new version of libraries in to your site... and don't forget to make a back up copy before you do so, if you have changed anything in it ei. you're not using standard distribution) or download the modified DynAPI from Helmi www-site.
- Juho Risku / Helmi Staff http://www.visualway.com/helmi
From: Tomlins Diane <[EMAIL PROTECTED]> Reply-To: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: [Dynapi-Help] Possible conflict with DynAPI ? Date: Mon, 4 Aug 2003 15:29:58 -0500
Hi all :)
I have a problem and I'm not expert enough with advanced JS to figure this one out myself. I have a site in which I use DynAPI and the LoadPanel to display about 90% of my content. I think the DynAPI version I'm using is either 2.5.6 or 2.5.7 as the site was created over a year ago.
It is now necessary for me to change the menu system a bit and I've
incorporated new menus using a Dreamweaver extension that plugs in all the
scripting. Now that I've done that and the new menus work, the LoadPanel has
totally ceased to function. I've spent days crawling thru the codes and
cannot find what's preventing the DynAPI from working. I have to solve this
or scrap the new menus.
I realize the new menu system with DynAPI 3.0 would probably work, but my
question then becomes what else, if anything, would break in the switch from
2.56/2.57 to 3.0 ??
If any one of you DynAPI wizards would consider looking at the current
'mixed' code and helping me find the conflict (or determine if one exists at
all), I'd be grateful for the assistance. If DynAPI 3.0 is the answer
instead, then I'd need to know where to find the info needed to put this
into place.
Thanks in advance, Diane
------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 _______________________________________________ Dynapi-Help mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dynapi-help
_________________________________________________________________
The new MSN 8: smart spam protection and 2 months FREE* http://join.msn.com/?page=features/junkmail
------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 _______________________________________________ Dynapi-Help mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dynapi-help
