What project are you doing? ----- Original Message ----- From: Cory Samaha To: [email protected] Sent: Tuesday, April 20, 2010 2:31 PM Subject: RE: accessing the GW Toolkit from JScript
Ah, I was afraid that might be the case. Perhaps doing this project using JScript was my mistake <smile>. Thanks Aaron for looking into it. -Cory From: Aaron Smith [mailto:[email protected]] Sent: Tuesday, April 20, 2010 5:10 PM To: [email protected] Subject: Re: accessing the GW Toolkit from JScript This problem appears to be unrelated to Window-Eyes. Using WSF, I can demonstrate this problem between VBScript and JScript without Window-Eyes involved: <job id="SharedObjectExample"> <script language="VBScript"> Class MyClassDefinition Private theObject Public Sub Class_Initialize() Set theObject = Nothing End Sub Public Property Get KeyStrings() Set KeyStrings = theObject End Property Public Property Set KeyStrings(stringObj) Set theObject = stringObj End Property End Class Function CreateMyClass() Set CreateMyClass = New MyClassDefinition End function </script> <script language="JScript"> x = CreateMyClass(); fsObj = new ActiveXObject("Scripting.FileSystemObject"); x.KeyStrings = fsObj </script> </job> Run this, as you will get the same "Object doesn't support this property or method" on the line x.KeyStrings = fsObj. VBscript to VBScript works. JScript to JScript works. VBScript to JScript works. But JScript to VBScript does not. Fortunately, I can work around this issue in the toolkit, and will do so in a future version. Aaron On 4/19/2010 4:25 PM, Cory Samaha wrote: Ok, thanks much. From: Aaron Smith [mailto:[email protected]] Sent: Monday, April 19, 2010 4:20 PM To: [email protected] Subject: Re: accessing the GW Toolkit from JScript Cory, I can now duplicate what you're talking about. Let me do some investigation. Aaron On 4/19/2010 4:03 PM, Cory Samaha wrote: Aaron, When I do print(Utilities.TypeName(x)); I get HotkeyManagerClass and when I do print(Utilities.TypeName(theStrings)); I get Dictionary From: Aaron Smith [mailto:[email protected]] Sent: Monday, April 19, 2010 3:55 PM To: [email protected] Subject: Re: accessing the GW Toolkit from JScript Cory, What do you get back if you use the Window-Eyes TypeName method, like this: print(Utilities.TypeName(x)); Aaron On 4/19/2010 3:49 PM, Cory Samaha wrote: Ah, got it. Now I'm back to the same message Error: Object doesn't support this property or method. Below is the output of what I typed in Immed. x = SharedObjects("com.GWMicro.GWToolkit.HotkeyManager").NewDialog(); x.IniFileName = "blah.ini"; x.IniSectionName = "hotkeys"; theStrings = strings("AIM.xml"); print(typeof(theStrings)); object x.KeyStrings = theStrings; Error: Object doesn't support this property or method From: Aaron Smith [mailto:[email protected]] Sent: Monday, April 19, 2010 3:40 PM To: [email protected] Subject: Re: accessing the GW Toolkit from JScript Sorry, I was going from memory. Use theStrings rather than myStrings, as myStrings is already defined in the Immed script. Aaron On 4/19/2010 2:59 PM, Cory Samaha wrote: Aaron, When I do typeof(myStrings); I get back that it's of type object. Did you say this ran fine for you in immed? I was trying this in a jScript .js file that I was writing, but just to compare I just tried launching the hotkey manager in immed as well and didn't have much luck there either. As soon as I tried to execute the line that says x.KeyStrings = myStrings; I get the following immed.js - Microsoft JScript runtime error Line 187 Column 5 'undefined' is null or not an object < 0x800A138F > So either way, both typing this out in immed or from a regular .js file that I run from the WE script manager, I can't get this to work. -Cory From: Aaron Smith [mailto:[email protected]] Sent: Monday, April 19, 2010 9:07 AM To: [email protected] Subject: Re: accessing the GW Toolkit from JScript Cory, What do you get for the type of myStrings? Aaron On 4/19/2010 8:52 AM, Cory Samaha wrote: Aaron, I tried x.KeyStrings = myStrings; and I get Object doesn't support this property or method < 0x800A01B6 > In fact, I first tried this without the parentheses and when I was unsuccessful I moved on to including parentheses. -Cory From: Aaron Smith [mailto:[email protected]] Sent: Monday, April 19, 2010 8:45 AM To: [email protected] Subject: Re: accessing the GW Toolkit from JScript 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 aWindow-Eyes hosted JScript script? In the following lines of code, I'mtrying to launch the hotkey manager. I haven't gotten to add keys yet, Ijust want to make sure I can launch it first. The following produces anerror. Note that myStrings is a variable previously defined and I haveconfirmed 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'veseen places where keyStrings() is used both with and without parenthesesafter it. I know that VBScript is less picky about the inclusion ofparentheses, but just in case, I tried that line omitting the parentheses asin 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 evertried to do this? Any thoughts? Thanks,Cory -- Aaron Smith Product Support Specialist * Web DevelopmentGW Micro, Inc. * 725 Airport North Office Park, Fort Wayne, IN 46825260-489-3671 * gwmicro.com To insure that you receive proper support, please include all pastcorrespondence (where applicable), and any relevant informationpertinent to your situation when submitting a problem report to the GWMicro Technical Support Team. -- Aaron Smith Product Support Specialist * Web DevelopmentGW Micro, Inc. * 725 Airport North Office Park, Fort Wayne, IN 46825260-489-3671 * gwmicro.com To insure that you receive proper support, please include all pastcorrespondence (where applicable), and any relevant informationpertinent to your situation when submitting a problem report to the GWMicro Technical Support Team. -- Aaron Smith Product Support Specialist * Web DevelopmentGW Micro, Inc. * 725 Airport North Office Park, Fort Wayne, IN 46825260-489-3671 * gwmicro.com To insure that you receive proper support, please include all pastcorrespondence (where applicable), and any relevant informationpertinent to your situation when submitting a problem report to the GWMicro Technical Support Team. -- Aaron Smith Product Support Specialist * Web DevelopmentGW Micro, Inc. * 725 Airport North Office Park, Fort Wayne, IN 46825260-489-3671 * gwmicro.com To insure that you receive proper support, please include all pastcorrespondence (where applicable), and any relevant informationpertinent to your situation when submitting a problem report to the GWMicro Technical Support Team. -- Aaron Smith Product Support Specialist * Web DevelopmentGW Micro, Inc. * 725 Airport North Office Park, Fort Wayne, IN 46825260-489-3671 * gwmicro.com To insure that you receive proper support, please include all pastcorrespondence (where applicable), and any relevant informationpertinent to your situation when submitting a problem report to the GWMicro Technical Support Team. -- Aaron Smith Product Support Specialist * Web DevelopmentGW Micro, Inc. * 725 Airport North Office Park, Fort Wayne, IN 46825260-489-3671 * gwmicro.com To insure that you receive proper support, please include all pastcorrespondence (where applicable), and any relevant informationpertinent to your situation when submitting a problem report to the GWMicro Technical Support Team.
