I admit that I have had to enter some information, then create a test
Cabrillo log file and see if the station data made any sense. If you look
around with the mouse pointer or invisible cursor, you may be able to deduce
the order of the fields. They are trying to crowd a lot of information into
a small screen, so misalignment between field names and field data occurs
frequently. There might be a particular font size and window size that would
improve this, but I'm not sure.
73,
Lloyd Rasmussen, W3IUU, Kensington, MD
http://lras.home.sprynet.com
-----Original Message-----
From: Doug Payne
Sent: Saturday, May 09, 2015 1:54 PM
To: [log in to unmask]
Subject: RE: N1MM+ Accessibility
HI,
Thanks for the suggestions. I ended up using N3FJP's 7QP logging software,
because I ran into problems with N1MM+. Specifically, I was not able to
enter my station information. The edit boxes were not labeled correctly. The
first several edit controls in the tab order were not labeled at all, and
the remaining controls had the wrong labels associated with them. I was
using JAWS 16 on Windows 7 SP1. Have any of you encountered this? How did
you work around it? Thanks.
--Doug, AC7T
-----Original Message-----
From: For blind ham radio operators [mailto:[log in to unmask]]
On Behalf Of Lloyd Rasmussen
Sent: Friday, May 01, 2015 9:28 AM
To: [log in to unmask]
Subject: Re: N1MM+ Accessibility
I also get this result in Window-Eyes. When I set up for a particular
contest, I use the Window-Eyes "label field" hotkey to label "testfoo" as
"call", then tab into the other fields for that contest and label them
appropriately. I must then save this change in the SET file associated with
N1MM+. If the configuration of my windows changes, this information, which
is associated with screen co-ordinates, becomes invalid. When this works, it
works quite well. And if it doesn't, you know that TestFoo means callsign if
you are not sure which field you are in. One could put testfoo into an
exception dictionary and have it say call, but I would rather try to get all
the fields labeled.
I haven't had much time lately to refine N1MM+ or to give the developers
more feedback, but I used it for about 15 contests since last summer.
73, W3IUU
-----Original Message-----
>From: David W Wood <[log in to unmask]>
>Sent: May 1, 2015 8:46 AM
>To: [log in to unmask]
>Subject: Re: N1MM+ Accessibility
>
>Doug I totally agree with you, but it is easier than a lot of others!
>
>A query.
>When I go into the call field by tabbing, or pressing F12, both in
>speech and Braille I am presented with a legend of "testfoo"
>
>Have you noticed this?
>
>73
>
>David W Wood
>
>-----Original Message-----
>From: For blind ham radio operators
>[mailto:[log in to unmask]]
>On Behalf Of Doug Payne
>Sent: Friday, May 01, 2015 6:34 AM
>To: [log in to unmask]
>Subject: N1MM+ Accessibility
>
>HI,
>
>
>
>I'll be operating in the 7th Area QSO Party this weekend. I'm
>considering trying N1MM+ for logging. I've used N1MM in the past, and
>while it's not accessible, I am able to use it with some success. Have
>others on the list tried N1MM+? How does it compare? Any tips or tricks in
setting it up?
>
>
>
>The greatest difficulty I had in using N1MM was with the
>"configurator". I had to frequently use the JAWS cursor while setting
>things up, and even then it didn't always work. I didn't use any of the
>fancier features of N1MM, such as the spots window, the dupe sheet, etc.
>
>
>
>If you hear me on during the contest, stop by and give me a point.
>Thanks a lot.
>
>
>
>--Doug, AC7T
|
