Aaron, you're a bit wrong here.
We specifically look for encrypted scripts in wsf files, but all other
wsf files get passed to Windows Script Host. They'll work with WE, but
only in the way that any external program will. That is, they'll have
to create a WindowEyes.Application object and identify themselves as a
script, and they won't have access to any of the methods of the Script
object.
Aaron Smith wrote:
Tim,
Are you referring to WSF files? If so, then, yes, you can use those.
You'll note the extension to an encrypted script file ends in .WSF.
VBF files, from what I've gathered, are Outlook Free/Busy files.
You might, however, investigate the Shared Objects feature of
Window-Eyes script. This is a built-in method of being able to share
objects across scripts. In fact, it's the main point of the GW Toolkit
script.
Aaron
Tim Burgess wrote:
Hi,
Is the use of .vbf files supported with Window Eyes? I'd like to
modularise
a large amount of code, if possible.
Best wishes.
Tim Burgess
Raised Bar Ltd
PO Box 4442
Atherstone
Warwickshire
CV9 9AT
Phone: +44 (0)1827 719822
Email: [EMAIL PROTECTED]
Web: http://www.raisedbar.net
Don't forget to vote for improved access to music and music
technology at
http://www.raisedbar.net/petition.htm
