[jawsscripts] Re: Jaws Scripts and WPF AutomationProperties.HelpText property value
- From: "Jacob Kruger" <jacobk@xxxxxxxxxxxxxx>
- To: <jawsscripts@xxxxxxxxxxxxx>
- Date: Sun, 11 Oct 2009 18:17:19 +0200
Fact is even recompiling version 10's scripts didn't help for some of the
issues, so will probably wait for another version of 11 before trying all of
this out again.
Secondly, with regard to recompiling all the scripts in one
directory/folder, it could be done with a form of command prompt batch file
where you could loop through all files of a certain type in the folder, and
execute a command line command to get each of them compiled one by one, but,
to be honest it's been quite a while since last did any real batch file
programming/scripting, but anyway.
Stay well
Jacob Kruger
Blind Biker
Skype: BlindZA
'...fate had broken his body, but not his spirit...'
----- Original Message -----
From: "Donald Marang" <donald.marang@xxxxxxxxx>
To: <jawsscripts@xxxxxxxxxxxxx>
Sent: Friday, October 09, 2009 1:27 PM
Subject: [jawsscripts] Re: Jaws Scripts and WPF
AutomationProperties.HelpText property value
>I realized that I was not clear in my last message. I think I got confused
> as well!
>
> To clear up the problem, I needed to run the JSX installer for my JAWS 10
> scripts to get "Internet Explorer_fs.jsb" file recompiled for just my
> DirecTV script package. This package includes a script that gets merged
> with the scripts for Internet Explorer and Firefox. This is completely
> unexpected and the questions I asked about recompiling the entire
> directory
> would help, but I still would not have thought it was necessary to
> recompile
> all scripts installed in older versions of JAWS when installing a new
> version! I was not even using JAWS 11 yet, except for a quick look at
> ResearchIt.
>
> Don Marang
>
>
> ----- Original Message -----
> From: "Jacob Kruger" <Jacob.Kruger@xxxxxxxxxxxx>
> To: <jawsscripts@xxxxxxxxxxxxx>
> Sent: Friday, October 09, 2009 3:50 AM
> Subject: [jawsscripts] Re: Jaws Scripts and WPF
> AutomationProperties.HelpText property value
>
>
>> Well, funny enough, and might not be relevant at all, but one other thing
>> I noticed (don't know exactly when it happened though) was that could no
>> longer read the contents of the internet explorer 7 address bar until I
>> took jaws 11 off again, and this is either trying to just focus on it,
>> and
>> copy contents to clipboard, which worked, although both versions of jaws
>> were saying, nothing selected, and I could also not read it character by
>> character, but this is now working again after removing jaws 11.
>>
>> Suppose this might also be related to what you mention about DOM as such,
>> but not sure, and only realized it seemed to be linked after finishing
>> testing/uninstalling, and had actually thought it might have been related
>> to some or other toolbar/add in for IE itself.
>>
>> Stay well
>>
>> Jacob Kruger
>> jacob.kruger@xxxxxxxxxxxx
>>
>>
>> -----Original Message-----
>> From: jawsscripts-bounce@xxxxxxxxxxxxx
>> [mailto:jawsscripts-bounce@xxxxxxxxxxxxx] On Behalf Of Donald Marang
>> Sent: Thursday, October 08, 2009 11:13 PM
>> To: jawsscripts@xxxxxxxxxxxxx
>> Subject: [jawsscripts] Re: Jaws Scripts and WPF
>> AutomationProperties.HelpText property value
>>
>> Hi Jacob,
>>
>> The JAWS 11 beta(#2) certainly changed something within shared
>> components.
>> I had a similar problem where JAWS 10 scripts to do simple walking
>> through
>> the DOM in Internet Explorer 7 simply stopped working just by installing
>> the
>> beta! I was able to restore the JAWS 10 scripts by uninstalling JAWS 11
>> beta including shared components, then installing JAWS 10 again! I asked
>> on
>> this list and the jaws-users list if anyone else had noticed this type of
>> issue. As I was writing the bug report, Eric Dameri had privately
>> emailed
>> me about the problem! I don't think FS wants these kinds of issues. I
>> finally discovered that I could resolve the problem by reinstalling all
>> of
>> the applications that I installed into version 11 with JSX after I
>> installed
>> the first beta. Once I reinstalled all such applications this way, which
>> in
>> my case is about 6 installs, the problem went away. In my case, I
>> assumed
>> that there must have been a change in the way that it would compile
>> "Internet Explorer.jsb" by the second beta. I know that reinstalling
>> all
>> of these JSX installs for each new version is required, but I did not
>> realize this was necessary for each update! Actually, this has slowed me
>> down in installing the latest update. Is there a simpler way to
>> recompile
>> all scripts?
>>
>> Don Marang
>>
>>
>> ----- Original Message -----
>> From: "Jacob Kruger" <Jacob.Kruger@xxxxxxxxxxxx>
>> To: <jawsscripts@xxxxxxxxxxxxx>
>> Sent: Thursday, October 08, 2009 7:06 AM
>> Subject: [jawsscripts] Re: Jaws Scripts and WPF
>> AutomationProperties.HelpText property value
>>
>>
>>> Sorry.
>>>
>>> WPF (windows presentation foundation) is microsofts new user interface
>>> technology/protocol, that's apparently soon to be used in most parts of
>>> their newer stuff, and I've also been trying it out/testing development
>>> therein myself using visual studio.net 2008 (VS.Net 2008), and trying to
>>> see if I can get jaws to work well enough with it to allow me to test my
>>> applications etc. etc.
>>>
>>> This is what the User Interface Automation that's now supposed to be
>>> being
>>> put into jaws 11 should be targeting as well, and that's why was talking
>>> about using functions that have been around in jaws scripting from
>>> before,
>>> but which seem to work a bit better/differently now in jaws 11.
>>>
>>> Another problem haven't mentioned yet though is that since started
>>> trying
>>> out jaws 11.0.611 beta this morning, it's actually interfering with
>>> other
>>> scripting we already made use of in VS.Net - I think so anyway - and
>>> seems
>>> to also be making earlier version of jaws 10 react incorrectly even
>>> though
>>> tried cleaning up that version of jaws with a clean install, but the
>>> moment had tested jaws 11 again, it wouldn't do what was meant to in the
>>> VS.Net development environment, almost as if jaws 11 was making changes
>>> to/adding onto the prior versions interface handling or something.
>>>
>>> Have just uninstalled it, and will see if version 10 now works again
>>> properly, might try out 11.0.534 again since don't think it was causing
>>> any hassles, and will be logging this on the beta test page.
>>>
>>> Stay well
>>>
>>> Jacob Kruger
>>> jacob.kruger@xxxxxxxxxxxx
>>>
>>> -----Original Message-----
>>> From: jawsscripts-bounce@xxxxxxxxxxxxx
>>> [mailto:jawsscripts-bounce@xxxxxxxxxxxxx] On Behalf Of Geoff Chapman
>>> Sent: Thursday, October 08, 2009 1:50 PM
>>> To: jawsscripts@xxxxxxxxxxxxx
>>> Subject: [jawsscripts] Re: Jaws Scripts and WPF
>>> AutomationProperties.HelpText property value
>>>
>>> dar jacob.
>>>
>>> man would you care to do a reread, then a quick doubletake/repost of
>>> what
>>> you were attempting to convey below? I'm kinda having some trouble
>>> sorting
>>> it exactly? <grin.>
>>>
>>> of course it doesn't help that I don't know what WPF is exactly as yet,
>>> but
>>> ... still, sounds like it might've perhaps been related to some other
>>> thread
>>> that I've somehow missed picking up on or something?
>>>
>>> could you reenlighten us a tad?
>>>
>>> thanks.
>>>
>>> From: "Jacob Kruger" <Jacob.Kruger@xxxxxxxxxxxx>
>>> To: <program-l@xxxxxxxxxxxxx>
>>> Cc: <jawsscripts@xxxxxxxxxxxxx>
>>> Sent: Thursday, October 08, 2009 5:02 PM
>>> Subject: [jawsscripts] Jaws Scripts and WPF
>>> AutomationProperties.HelpText
>>> property value
>>>
>>>
>>>> Just found a jaws scripting function that seems to have been there in
>>>> jaws
>>> 10 as well, but now in jaws 11, the GetObjectHelp() function does in
>>> fact
>>> return the new control/object attribute from within WPF that they all
>>> seemed
>>> to think it would be making use of since started looking at any
>>> accessibility guidelines for WPF etc. This is the
>>> AutomationProperties.HelpText attribute/property for the controls, and
>>> it's
>>> contents can also be databound as such, so you could to a certain extent
>>> control the rendered content dynamically as such.
>>>>
>>>> It still however doesn't seem to be getting mentioned by jaws
>>> automatically as such, unless you hit the jaws key + F1 key, it'll be
>>> included as what is then called context help.
>>>>
>>>> Currently testing with jaws 11.0.611 beta version for this type of
>>>> thing.
>>>>
>>>> Stay well
>>>>
>>>> Jacob Kruger
>>>> jacob.kruger@xxxxxxxxxxxx
>>>>
>>>>
>>>> __________
>>>> Visit and contribute to The JAWS Script Repository
>>>> http://jawsscripts.com
>>>>
>>>> View the list's information and change your settings at
>>>> //www.freelists.org/list/jawsscripts
>>>>
>>>
>>> __________
>>> Visit and contribute to The JAWS Script Repository
>>> http://jawsscripts.com
>>>
>>> View the list's information and change your settings at
>>> //www.freelists.org/list/jawsscripts
>>>
>>>
>>> No virus found in this incoming message.
>>> Checked by AVG - www.avg.com
>>> Version: 8.5.421 / Virus Database: 270.14.7/2422 - Release Date:
>>> 10/08/09
>>> 06:39:00
>>> __________
>>> Visit and contribute to The JAWS Script Repository
>>> http://jawsscripts.com
>>>
>>> View the list's information and change your settings at
>>> //www.freelists.org/list/jawsscripts
>>>
>>
>> __________
>> Visit and contribute to The JAWS Script Repository http://jawsscripts.com
>>
>> View the list's information and change your settings at
>> //www.freelists.org/list/jawsscripts
>>
>>
>> No virus found in this incoming message.
>> Checked by AVG - www.avg.com
>> Version: 8.5.421 / Virus Database: 270.14.7/2422 - Release Date: 10/08/09
>> 06:39:00
>> __________
>> Visit and contribute to The JAWS Script Repository http://jawsscripts.com
>>
>> View the list's information and change your settings at
>> //www.freelists.org/list/jawsscripts
>>
>>
>
> __________
> Visit and contribute to The JAWS Script Repository http://jawsscripts.com
>
> View the list's information and change your settings at
> //www.freelists.org/list/jawsscripts
>
>
> __________ Information from ESET NOD32 Antivirus, version of virus
> signature database 4494 (20091009) __________
>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>
>
__________ Information from ESET NOD32 Antivirus, version of virus signature
database 4497 (20091011) __________
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com
__________
Visit and contribute to The JAWS Script Repository http://jawsscripts.com
View the list's information and change your settings at
//www.freelists.org/list/jawsscripts
Other related posts:
