The GW-Scripting list is a discussion list for information regarding the development and use of Window-Eyes scripts. Any subscriber of the GW-Scripting list has the ability to post on-topic messages.
From:
Tom Kingston <tom.kingston@charter.net>Subject:
Re: how to know what to reclass controls as when encounteredDate:
Sun, Nov 27, 2011 1:07:40 pmBecause Window-Eyes supports the VBScript and JScript engines directly.
So it cuts down on the overhead considerably and makes scripting much
easier.
Regards,
Tom
On 11/27/2011 11:30 AM, Katherine Moss wrote:
> Oh dang. Nice! Now VBScript I do understand a little bit just as I do with C#. And that's another question that's been burning inside of me for a long time. How come we never see apps written in C#?
>
> -----Original Message-----
> From: Jared Wright [mailto:wright.jaredm@gmail.com]
> Sent: Sunday, November 27, 2011 11:27 AM
> To: gw-scripting@gwmicro.com
> Subject: Re: how to know what to reclass controls as when encountered
>
> Think of Immed as an interactive interpreter for WE apps written in VBScript or JScript.
> On 11/26/2011 8:59 PM, Katherine Moss wrote:
>> Is that a mode you can open? I don't use WE much right now because it's kind of pointless having to restart my computer every half an hour. I hope to purchase it within the week though.
>>
>> -----Original Message-----
>> From: Tom Kingston [mailto:tom.kingston@charter.net]
>> Sent: Saturday, November 26, 2011 7:51 PM
>> To: gw-scripting@gwmicro.com
>> Subject: Re: how to know what to reclass controls as when encountered
>>
>> Just to add to what Chip said, sometimes, if you're lucky, a simple look at the control in the immediate mode window will do the trick. I just opened a program wherein I knew I had some good examples. And here's all I did.
>> 1. Focus the custom control.
>> 2. Open the Immediate mode window.
>> 3. Enter the following and note the result.
>> Print FocusedWindow.ClassName
>> sfppack2Bld1503TrackbarClass
>> From that I know it's just a custom track bar and reclass it as a track bar.
>> But this is the luck of the draw. Sometimes class names are informative or at least give you a potential clue or hint as to what to try.
>>
>> Otherwise it's a matter of trying to figure the control out by evaluating its functionality. And sometimes these custom controls look virtually no different than their standard counterparts. So borrowing a pair of knowledgeable eyes can sometimes reveal their secret.
>>
>> Good luck,
>> Tom
>>
>>
>>
>> On 11/26/2011 7:34 PM, Chip Orange wrote:
>>> Hi Katherine,
>>>
>>> I'm afraid you can't reclass unless you have a pretty good idea as to
>>> what it should be.
>>>
>>> If you're a scripter, you can use the various scripting tools to take
>>> a look at the control's name or class (which often gives you a hint
>>> as to what it's being used for), or the MSAA info log using the WE
>>> Event app might tell you something.
>>>
>>> If you're not a scripter, then you are usually left to trial and
>>> error (and a lot of the time, you have to set it back to "original"
>>> because whatever you chose is worse than what it was doing).
>>>
>>> Sorry it's not easier than that, but if it is, I'm afraid I don't
>>> know about it.
>>>
>>> Chip
>>>
>>>
>>> _____
>>>
>>> From: Katherine Moss [mailto:Katherine.Moss@gordon.edu]
>>> Sent: Saturday, November 26, 2011 7:19 PM
>>> To: gw-scripting@gwmicro.com
>>> Subject: how to know what to reclass controls as when encountered
>>>
>>>
>>>
>>> Hello all,
>>>
>>> I was fooling around a few weeks ago with the WCF
>>> service configuration editor (a tool in the Windows SDK that I will
>>> need in future development endeavors), and I realized that some of
>>> the controls were custom according to WE, so I made an attempt at
>>> reclassing them. I reclassed them as buttons not knowing what they
>>> were actually supposed to be, and whatever I did, that seemed to make
>>> them all disjunct and unreadable. WE could read them, but it sounded
>>> like Gibberish rather than English. What is the first step when trying to reclass a control in figuring out what it should be?
>>> Thanks guys.
>>>
>>>
>>>
>>> Katherine Moss,
>>>
>>> Administrator of the AccessCop Network, previously Raeder24.org.
>>> Visit us on the web at http://raeder24.org<http://raeder24.org/>;
>>>
>>>
>>>
>>>
>>
>
>
So it cuts down on the overhead considerably and makes scripting much
easier.
Regards,
Tom
On 11/27/2011 11:30 AM, Katherine Moss wrote:
> Oh dang. Nice! Now VBScript I do understand a little bit just as I do with C#. And that's another question that's been burning inside of me for a long time. How come we never see apps written in C#?
>
> -----Original Message-----
> From: Jared Wright [mailto:wright.jaredm@gmail.com]
> Sent: Sunday, November 27, 2011 11:27 AM
> To: gw-scripting@gwmicro.com
> Subject: Re: how to know what to reclass controls as when encountered
>
> Think of Immed as an interactive interpreter for WE apps written in VBScript or JScript.
> On 11/26/2011 8:59 PM, Katherine Moss wrote:
>> Is that a mode you can open? I don't use WE much right now because it's kind of pointless having to restart my computer every half an hour. I hope to purchase it within the week though.
>>
>> -----Original Message-----
>> From: Tom Kingston [mailto:tom.kingston@charter.net]
>> Sent: Saturday, November 26, 2011 7:51 PM
>> To: gw-scripting@gwmicro.com
>> Subject: Re: how to know what to reclass controls as when encountered
>>
>> Just to add to what Chip said, sometimes, if you're lucky, a simple look at the control in the immediate mode window will do the trick. I just opened a program wherein I knew I had some good examples. And here's all I did.
>> 1. Focus the custom control.
>> 2. Open the Immediate mode window.
>> 3. Enter the following and note the result.
>> Print FocusedWindow.ClassName
>> sfppack2Bld1503TrackbarClass
>> From that I know it's just a custom track bar and reclass it as a track bar.
>> But this is the luck of the draw. Sometimes class names are informative or at least give you a potential clue or hint as to what to try.
>>
>> Otherwise it's a matter of trying to figure the control out by evaluating its functionality. And sometimes these custom controls look virtually no different than their standard counterparts. So borrowing a pair of knowledgeable eyes can sometimes reveal their secret.
>>
>> Good luck,
>> Tom
>>
>>
>>
>> On 11/26/2011 7:34 PM, Chip Orange wrote:
>>> Hi Katherine,
>>>
>>> I'm afraid you can't reclass unless you have a pretty good idea as to
>>> what it should be.
>>>
>>> If you're a scripter, you can use the various scripting tools to take
>>> a look at the control's name or class (which often gives you a hint
>>> as to what it's being used for), or the MSAA info log using the WE
>>> Event app might tell you something.
>>>
>>> If you're not a scripter, then you are usually left to trial and
>>> error (and a lot of the time, you have to set it back to "original"
>>> because whatever you chose is worse than what it was doing).
>>>
>>> Sorry it's not easier than that, but if it is, I'm afraid I don't
>>> know about it.
>>>
>>> Chip
>>>
>>>
>>> _____
>>>
>>> From: Katherine Moss [mailto:Katherine.Moss@gordon.edu]
>>> Sent: Saturday, November 26, 2011 7:19 PM
>>> To: gw-scripting@gwmicro.com
>>> Subject: how to know what to reclass controls as when encountered
>>>
>>>
>>>
>>> Hello all,
>>>
>>> I was fooling around a few weeks ago with the WCF
>>> service configuration editor (a tool in the Windows SDK that I will
>>> need in future development endeavors), and I realized that some of
>>> the controls were custom according to WE, so I made an attempt at
>>> reclassing them. I reclassed them as buttons not knowing what they
>>> were actually supposed to be, and whatever I did, that seemed to make
>>> them all disjunct and unreadable. WE could read them, but it sounded
>>> like Gibberish rather than English. What is the first step when trying to reclass a control in figuring out what it should be?
>>> Thanks guys.
>>>
>>>
>>>
>>> Katherine Moss,
>>>
>>> Administrator of the AccessCop Network, previously Raeder24.org.
>>> Visit us on the web at http://raeder24.org<http://raeder24.org/>;
>>>
>>>
>>>
>>>
>>
>
>
