Greg,

Sorry to be an idiot, I realized you worked hard to idiot proof the docs on the XNav package. You mention I should just be able to add the vbs pieces to a jscript program, but I'm curious, do I need to add the .vbs versions of all of the normal commands as well as the jscript version?

I tried the obvious:

Original .swx file:

You still have SkunkNav.js in your file list. If you've switched your code over to call Xnav instead, there's no reason to keep loading SkunkNav. It's possible that doing so is causing some function name collisions.

Similarly, you don't need both SkapiDefs.js and SkapiDefs.vbs. One or the other is sufficient. All public names defined in any script file are visible to every other script file, regardless of language.

Also you have lib="True" on all the Xnav files. This means that SkunkWorks will look for those files under your SkunkWorks\Libraries folder rather than under your project folder. Double-check that you've actually put the Xnav files where your .swx file says you did, i.e. in SkunkWorks\Libraries\xnav.

Apart from that, what you've done looks right. If you're still getting errors, post the specifics and I'll try to make sense of them.

It makes sense when you mention it that I'm having skunknav v. xnav issues.

Thanks for the info that I dont have to duplicate the .js and .vbs defs files.

I did put the xnav under libraries assuming I'll want to access it from multiple places, but good catch.

Thanks,
-t