Hi all,
You're all going to love me (not), as I've just checked in a whole load of stuff which (almost) requires a DLL update. (I know not everyone who takes CVS copies can actually build the DLL from the source.) I'm on a mission to try and eliminate all script errors, particularly now I've realised that the error message always quotes search.htm as the file, regardless of the true location - this makes it fantastically difficult for people without script debuggers to offer useful feedback on the errors. To this end, I've made the following changes: Added various bits of exception handling around the place with messageboxes containing sensible (to me) sounding error messages if calls fail. This includes code to catch errors in XML searches (as reported by MLL). The error message in this case is rather techy (it contains the search code), but as this is really to help developers, I think that's OK. Added a new method to ILauncher on DQSDTools.dll which can verify that the DLL is of a specified version. Added a new JS module (version.js) which at startup checks in a controlled fashion that A. the DQSDTools DLL is available and A. that it's the correct version. It's down to anyone creating a dependency between revisions to the DLL and the scripts to bump the version resource _and_ the values in version.js. Cheers, Will _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm _______________________________________________ Dqsd-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dqsd-users http://sourceforge.net/mailarchive/forum.php?forum_id=8601
