David, I don't know why control backslash is working like that for you; it's very strange; I'd reboot if I were you to clear any weird condition, and I think it won't keep doing it. as for your script error; you didn't execute the script by clicking on it in a windows explorer window did you? that would start it run not as a window eyes script, but as a windows scripting host program, and so it wouldn't have access to the window eyes object model. Chip
_____ From: David [mailto:[email protected]] Sent: Saturday, January 09, 2010 12:05 PM To: Scripting List WE Subject: Script Framework Allright, I did download the Framework script from SC. And, well, I am not sure if it is only my system, but I did see another user recently complaint about this one script. I wonder if GW have been missing out on something, or if there is something I am doing wrong. First of all, whenever I press the CTRL-Backslash - to go to WE controlpanel - the Framework script starts, and I am asked to create a new script. Only way I have to go to my WE controlpanel, is by alt-tabbing to it. Frustrating! Second, I did go through the wizzard of the Framework script, and created a smal test script. Then tried to run it. And, what did I get? An error pointing me to the following line at the beginning of the script: Dim myINIFile : myINIFile = ClientInformation.ScriptPath & "\test.vbs.ini" It said, that the ClientInformation variable is undefined. Strange! This is a line GW has inserted (through the Framework), and the first thing I am told, is that it is wrong? I am confused. Why is it, that we download a script, that is meant to keep a standard, and it messes with the CTRL-Backslash hotkey, and creates a script that only knocks us in the head, with an error. Not exactly encouraging me to follow that standard! :) Anybody else is experiencing this?
