Thanks for re-posting this, David.
Scott doesn't seem to know why we are having this problem, but maybe it's
because I'm not asking the right questions in the right way.
If you want to ask him yourself, go ahead, and let's see what he says.
You can remind him that I'm having the problem too if that helps.
73from Tom Behler: KB8TYJ
----- Original Message -----
From: "David Simpson" <[log in to unmask]>
To: <[log in to unmask]>
Sent: Monday, October 10, 2011 11:42 PM
Subject: FW: Preliminary Observations of N3FJP's NAQP Logger with Various
Screen Readers.
> Hi.
> Since the PA QSO Party seems to have brought up the problem with the
> N3FJP logging software where it doesn't always type the first character in
> a
> field, I hope it will be okay to repost the observations I made on this,
> about two months ago. Rereading the message has served to remind me that I
> never did get a sighted person to watch as I make entries into N3FJP,
> while
> I use various screen readers, or none at all.
> I will make this one additional observation: I've been using the
> ACLog general logging program from N3FJP, and I don't have the missing
> character problem; I do have the problem when I use the Field Day log or
> some of the other contest logs. Maybe there's a clue there. Perhaps Scott
> Davis did something different in creating the ACLog.
> Dave
>
> -----Original Message-----
> From: David Simpson [mailto:[log in to unmask]]
> Sent: Tuesday, August 09, 2011 2:59 PM
> To: 'For blind ham radio operators'
> Subject: Preliminary Observations of N3FJP's NAQP Logger with Various
> Screen
> Readers.
>
> I just spent a half hour experimenting with the NAQP logging
> software from N3FJP. As I mentioned on the list, I have had problems
> entering data into it, when JAWS is running. Sometimes--but not
> always--when
> I enter a call sign or a name, the first character doesn't get entered,
> even though JAWS speaks it. Some people on the list have never had this
> problem; others have. As I mentioned in previous emails, I tried
> maximizing
> the screen, playing with the Zoom feature, unchecking the Toolbar, stuff
> like that. But, none of these actions corrected the problem.
> I just tried the program using just the N3FJP voice prompts, then
> with NVDA, and with SaToGo.
> Without any screen reader loaded, and just using the N3FJP voice
> prompts, I didn't have any problem with initial characters in a field not
> being entered.
> With SaToGo and no N3FJP prompts, I still had the problem. Also, for
> some reason, it reads the label on the Name and SPC fields o.k., but not
> the
> Call field.
> With NVDA and no voice prompts: mostly things worked o.k., although
> on the first entry out of maybe ten that I tried, I did miss the first
> letter of the call.
> I don't know what to make of these results. I think I will repeat
> the experiment in the company of a sighted person and see if any visual
> clues appear.
> Any thoughts or other suggestions of things to try?
>
> 73,
>
> Dave
>
> -----Original Message-----
> From: For blind ham radio operators [mailto:[log in to unmask]]
> On Behalf Of Steve
> Sent: Tuesday, August 09, 2011 2:22 PM
> To: [log in to unmask]
> Subject: Re: Does anyone else have this problem with the N3FJP logging
> software?
>
> I haven't tried it recently and in the past, I didn't have that particular
> problem of it not reading the complete field.
>
> The one thing I do recall having to do was to set up a frame restriction
> with Jaws so it wouldn't try to keep reading the time info.
>
> Steve, K8SP
>
|
