BLIND-HAMS Archives

For blind ham radio operators

BLIND-HAMS@LISTSERV.ICORS.ORG

Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"Howard, W A 9 Y B W" <[log in to unmask]>
Reply To:
For blind ham radio operators <[log in to unmask]>
Date:
Mon, 10 Oct 2011 08:50:39 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (42 lines)
Have you tried WindowEyes to see if the, entering the first character twice, 
problem still exists?

You can download a trial version for free.

I have had both WindowEyes and JAWS on the same system at the same time with 
no problems.  Note: this was with Windows XP though!!

Howard #3, W A 9 Y B W

----- Original Message ----- 
From: "Tom Behler" <[log in to unmask]>
To: <[log in to unmask]>
Sent: Monday, October 10, 2011 7:13 AM
Subject: Answer to the problem of dupe function not working correctly in P A 
Q P Software


> Hi, all.
>
> Just for anyone's information, Steve (KW3A) was correct.  I wrote to Scott
> Davis (N3FJP) about my duplicate function not working correctly until all
> info is entered, and he confirmed what Steve thought.
>
> Here's what Scott himself said:
>
> Quote:  With the state QSO parties, where rovers are allowed, there is no
> way for the program to know if it is a duplicate until both the call and 
> the
> county are entered.  End Of Quote."
>
>
> So, I guess this is something that will have to be worked around somehow 
> in
> the future.
>
> Now, if I can only solve the problem of often having to enter the first
> character in an entry field twice, I'll be all set.  Scott doesn't seem to
> have an answer for that one, and I am wondering if it is a Jaws issue.
>
> 73 from Tom Behler:  KB8TYJ 

ATOM RSS1 RSS2