Cory,

KeyStrings is a property, not a method, so you don't need the parenthesis. The following works for me in Immed:

x = SharedObjects("com.GWMicro.GWToolkit.HotkeyManager").NewDialog();
x.INIFileName = "blah.ini";
x.INISectionName = "Hotkeys";
myStrings = Strings("blah.xml");
x.KeyStrings = myStrings;

Aaron

On 4/18/2010 5:29 AM, Cory Samaha wrote:
Greetings all,

What is the accepted approach for accessing the GW Toolkit from a
Window-Eyes hosted JScript script?  In the following lines of code, I'm
trying to launch the hotkey manager.  I haven't gotten to add keys yet, I
just want to make sure I can launch it first.  The following produces an
error.  Note that myStrings is a variable previously defined and I have
confirmed that it works as it should.

var hotkeyManager =
SharedObjects("com.GWMicro.GWToolkit.HotkeyManager").newDialog();
hotkeyManager.INIFileName = iniFileName;
hotkeyManager.INISectionName = "Hotkeys";
hotkeyManager.KeyStrings() = myStrings;

I'm getting an error on the line that says hotkeyManager.KeyStrings() =
myStrings; which says

Cannot assign to a function result

<  0x800A138B>

In the GW toolkit documentation examples which use VBScript syntax, I've
seen places where keyStrings() is used both with and without parentheses
after it.  I know that VBScript is less picky about the inclusion of
parentheses, but just in case, I tried that line omitting the parentheses as
in the following line.

hotkeyManager.KeyStrings = myStrings;
Now I get the following error.

Object doesn't support this property or method

<  0x800A01B6>

So, obviously there is some syntax I'm not getting right.  Has anyone ever
tried to do this?  Any thoughts?

Thanks,
Cory


--
Aaron Smith
Product Support Specialist * Web Development
GW Micro, Inc. * 725 Airport North Office Park, Fort Wayne, IN 46825
260-489-3671 * gwmicro.com

To insure that you receive proper support, please include all past
correspondence (where applicable), and any relevant information
pertinent to your situation when submitting a problem report to the GW
Micro Technical Support Team.

Reply via email to