Hi Chip,
OK, like I had said, twisting around the object model and with all the
twists you have to grab the object of the object and finally get the object.
In other words you have the settings down the list which is referred to
from something up the list and so on...
A Pain but each time I forget this it takes a while to figure out that
twist.
So, in the end this is what works using the application assignment in
making an object (and could use Steve's win32 version as well, but I think I
ran into compiling issues with that one):
WeComputerVoice = CreateObject( "windoweyes.application")
WeComputerVoice.ActiveSettings.Screen.Rate = 42
This changes the screen rate to 42 and in order to preserve the original, I
probably have to and makes sense to store the original settings in another
object before the game starts, then restore at the end.
Now that I mastered this, down the road I will be using a set file for
this for just the game and anyone can eventually save there own preferences
at the game window I now have.
Thanks, Bruce
Sent: Thursday, May 24, 2012 10:30 PM
Subject: RE: No ScreenSettings property!
Hi Bruce,
Just to add to what Steve says, you are creating an application object, and
then trying to access a property of it named screenSettings. You get an
error, and one of the first things you should check is to make sure there is
such a property. In this case there is no property of the application
object named screenSettings.
When you look up the screenSettings object, it tells you in the help for the
object itself that it can only be access from a set file object as Steve
said.
hth,
Chip
> -----Original Message-----
> From: BT [mailto:b...@fltg.net]
> Sent: Thursday, May 24, 2012 7:36 PM
> To: gw-scripting@gwmicro.com
> Subject: No ScreenSettings property!
>
>
> Hi Chip,
>
> How come this does not work?
> WeComputerVoice = CreateObject( "windoweyes.application")
> WeComputerVoice.ScreenSettings.Rate = 62
>
> "Error, Raised Attribute Error!"
>
> The format for Speech works, but not the same format for
> ScreenSettings.
>
> Why is this?
> This is a Python format and not a .vbs so the Set command is
> not needed.
>
> Bruce
>
