[jawsscripts] Re: jawsscripts Digest V6 #31

  • From: Paul Bonarrigo <pjbonarrigo@xxxxxxxxx>
  • To: "jawsscripts@xxxxxxxxxxxxx" <jawsscripts@xxxxxxxxxxxxx>
  • Date: Sat, 18 Feb 2012 12:04:49 -0800 (PST)

Frame viewer issue.
If the app is old and the interface has little chance of changing, you can 
always use FindString in a script. You could do the same without a script but 
there is key gymnastics involved. I guess that's one of the beauties of scripts.

If I'm on a screen and want to get to 'CaseMgr Addr' field on that screen, I 
would activate the Jaws find dialog box, type 'CaseMgr Addr' as the string to 
find (ignore quotes). I would activate the Jaws cursor and execute the find. 
After a successful find, the Jaws cursor sits at the  the target find string. 
Route PC to Jaws and activate the PC cursor. You may need to tab or arrow to 
move the PC Cursor into the input field.

That's the hard core no script Jaws user.
Here's a pseudo script.
I use invisible cursor here.

var string sFindString
let sFindString = "CaseMgr Addr"

SaveCursor()
InvisibleCursor()
if( FindString(wHdl, sFindString, ... ) then
 RoutePCToInvisible()
 PCCursor()

 TabKey()
else
 SayString(sFindString+" not found.")

endif

You are of course dependent on the screen text and changes will break your 
script. If the frames work at least this brings the user to the screen area of 
interest. If the screen location of the string changes but the string text 
remains the same then I can argue for my find string script or key combo 
solution because the frame will point at the old screen location.



________________________________
 From: FreeLists Mailing List Manager <ecartis@xxxxxxxxxxxxx>
To: jawsscripts digest users <ecartis@xxxxxxxxxxxxx> 
Sent: Thursday, February 16, 2012 11:09 PM
Subject: jawsscripts Digest V6 #31
 
jawsscripts Digest    Thu, 16 Feb 2012    Volume: 06  Issue: 031

In This Issue:
        [jawsscripts] Re: Frame Viewer Issue
        [jawsscripts] jawsscripts, re-test

----------------------------------------------------------------------

From: "Geoff Chapman" <gch@xxxxxxxxxxxxxxxx>
Subject: [jawsscripts] Re: Frame Viewer Issue
Date: Thu, 16 Feb 2012 18:25:49 +1100

I presume You've looked into

http://www.hotspotclicker.org

have you? I was just thinking, maybe
after doing some OCR stuff on this app, if in the least successful,
and if mouse positioning on the OCRed stuff was reliable, you might be able 
to spot it up and bring some joy to driving it? you can have hotspot sets 
for various environs within the application also, which without having any 
way to swap frames in/out for a given app, you can't of course do with 
frames manager directly.


----- Original Message ----- 
From: "Tom R" <twr6444@xxxxxxxxx>
To: <jawsscripts@xxxxxxxxxxxxx>
Sent: Friday, February 10, 2012 5:28 AM
Subject: [jawsscripts] Re: Frame Viewer Issue


> Don.,
>
> The application is called ACSR by CSG and is used in cable, satellite tv, 
> and telephony call centers. It is a black box to me, however,
> when I created my frames, the app name comes up as xboi, so my frames file 
> is xboi.JFF. Just to note, this app appears to
> randomly abort when Jaws is running, even if the ACSR app is minimmized. I 
> have reported it to their IT group and have not had
> a response. This ACSR app is a monster with dozens of complex screens, 
> most of which are not accessability friendly. The app runs on a PC
> running windows xp and I am usinng Jaws 13.
>
> Thanks
> Tom
>
> ________________________________
> From: Don Mauck <don.mauck@xxxxxxxxxx>
> To: jawsscripts@xxxxxxxxxxxxx
> Sent: Thursday, February 9, 2012 11:01 AM
> Subject: [jawsscripts] Re: Frame Viewer Issue
>
> Tom what AS400 client are you using?
>
> -----Original Message-----
> From: Tom R [mailto:twr6444@xxxxxxxxx]
> Sent: Thursday, February 09, 2012 10:49 AM
> To: jawsscripts@xxxxxxxxxxxxx
> Subject: [jawsscripts] Re: Frame Viewer Issue
>
> Jackie, Don
>
> Thanks for the feedback, I appreciate it!
>
> Indeed, this is an AS400 application with fixed screen sizes that don't 
> seem to change often. The reason I am using frames primarily is that I am 
> very new to the scripting environment and under time pressure, but aren't 
> we all? :)
>
> I read the help documentation in depth, and verified that my validation 
> rules were correct. I found a work around by adding a dummy frame, with 
> the exact same validation rules on the active window. I could then move to 
> that frame. Once I stopped and relaunched Jaws, all the other frames were 
> now accessible and then I deleted the dummy frame. A mystery, but I got it 
> to work.
>
> What I am encountering in this app, is that several screens have areas 
> that I need to get the Jaws cursor to quickly, and then the normal Jaws 
> reading keys work fine.
> Getting to them was the issue so I used Frames with hotkeys. If there is a 
> simple script solution to this that you have an example of, I will use 
> that instead and spread my wings so to speak.
>
> I also discovered a bug in Jaws 13 that I will report to FS today. The 
> screen names in this app are ridiculously long, pretty much the entire 
> screen and often greater than 100 characters. When I create a frame, that 
> name is automatically entered as the window name validation field. When 
> you click on the Validation Rules Tab in Frame Viewer, Jaws abruptly 
> aborts with no error message, and the frame is not saved. I found a work 
> around by creating the frame without touching the Validation Rules tab, 
> closing frame viewer, opening the .JFF fle in notepad and manually 
> shortening the Window name. Then relaunching Frame Viewer I can continue. 
> A giant pain but it works.
>
> I am finding JAWS to be an incredibly powerful program with a steep 
> learning curve. The help I am getting here is fantastic.
>
> Thanks!
> Tom
>
> ________________________________
> From: Don Mauck <don.mauck@xxxxxxxxxx>
> To: jawsscripts@xxxxxxxxxxxxx
> Sent: Thursday, February 9, 2012 7:33 AM
> Subject: [jawsscripts] Re: Frame Viewer Issue
>
> I would also add that if for any reason the screen resolution gets altered 
> it will hose up any frames that you've created, I too do not like them 
> with the exception of true emulation screens such as AS400 or 3270 
> instances.
>
> -----Original Message-----
> From: Jackie McBride [mailto:abletec@xxxxxxxxx]
> Sent: Thursday, February 09, 2012 7:26 AM
> To: jawsscripts@xxxxxxxxxxxxx
> Subject: [jawsscripts] Re: Frame Viewer Issue
>
> Tom, have u checked the relevant help file regarding this? It's in the 
> Jaws help topics under customizing jaws > frame viewer. There's a 
> troubleshooting section under that. There's a lot of stuff that can go 
> wrong w/frames (I personally am not a huge fan for a variety of reasons, 
> but, yeah, sometimes they're good). U say u have the app open, so that's 
> likely not a consideration. Your next consideration is the validation 
> rules, so you'll need to check the frames' properties to make sure that 
> the rules are what u need them to be. Specifically, sometimes these rules 
> contain document titles, for example, which means they won't work when 
> another document is loaded. You'll also need to check that the 
> application's settings are in fact enabled in the jaws manage applications 
> settings dialog.
>
> 1 of the reasons I'm not a huge fan of frames is that they're seriously 
> resolution-dependent; thus, if u created a frame while the app was 
> maximized & then tried to make it work while the app is in the restored 
> state, it won't.
>
> I've also had situations where I created frames for an ap, & when it was 
> updated, of course the blippin things didn't work. W/that, I actually 
> ended up havin to delete 'em & start over.
>
> The reason I asked u to take a long hard look at that help file is simply 
> because, as u get into the guts of how frames work, it also kind of tips u 
> off to what could be going haywire.
>
> HTH.
>
> On 2/8/12, Tom R <twr6444@xxxxxxxxx> wrote:
>> Hi All,
>>
>> I am new to Jaws and having a problem with Frame Viewer I can't seem
>> to figure out.
>> I have successfully created quite a few frames, so I have a pretty
>> good handle on the process.
>>
>> Today I went to a screen that I had created 8 frames on earlier,
>> launched Frame Viewer and listed the frames. All 8 frames showed up on
>> my list, but non showed on the screen and the "Go to Frame" button was
>> greyed out. I am sure this is something simple I am missing.
>>
>> As always, any help is greatly appreciated.
>>
>> Tom Reinhardt
>> __________�
>>
>> View the list's information and change your settings at
>> //www.freelists.org/list/jawsscripts
>>
>>
>
>
> --
> Blame the computer--why not? It can't defend itself & occasionally might 
> even be the culprit Jackie McBride Ask Me Computer Questions at: 
> www.pcinquirer.com Jaws Scripting training materials: 
> www.screenreaderscripting.com
> homePage: www.abletec.serverheaven.net
> __________�
>
> View the list's information and change your settings at 
> //www.freelists.org/list/jawsscripts
>
> __________�
>
> View the list's information and change your settings at 
> //www.freelists.org/list/jawsscripts
> __________�
>
> View the list's information and change your settings at 
> //www.freelists.org/list/jawsscripts
>
> __________�
>
> View the list's information and change your settings at
> //www.freelists.org/list/jawsscripts
> __________�
>
> View the list's information and change your settings at
> //www.freelists.org/list/jawsscripts
> 


------------------------------

Date: Thu, 16 Feb 2012 08:46:21 +0000
From: Hamid AITOUZNAG <hamid.maier@xxxxxxxxx>
Subject: [jawsscripts] jawsscripts, re-test

Thanks a million Jackie...

All the best!!!

-- 
Hamid AITOUZNAG
"We never value what we have until we lose it!"
"Be careful how you treat people on your way up because you might meet them 
again on your way down!!!"
Skype: hamidgeni
Twitter: hamidgeni


------------------------------

End of jawsscripts Digest V6 #31
********************************
__________�

View the list's information and change your settings at 
//www.freelists.org/list/jawsscripts

Other related posts:

  • » [jawsscripts] Re: jawsscripts Digest V6 #31 - Paul Bonarrigo