[WriteLog] Re: Check Call Window - OK?

Eric Scace K3NA eric at K3NA.ORG
Sun Feb 23 23:32:53 EST 2003


   If a change is to be made, I would favor using BOTH color AND a text indicator.  Anything to reinforce the message to a sleepy
operator is good ergonomic design.

   Even better ergonomic design would be the consistent use of color across the various windows (e.g., bandmap, packet spot, super
check partial, check call).  I generally try to configure for a light gray background (generally used to indicate "data whose
content can not be modified from the keyboard"), red=dupe, green=ok to work, yellow=new mult (but yellow can not be used against a
white background), and black/gray in the super-check-partial window for "exists in the database but not worked in the contest on any
band"... but can't implement this scheme uniformly because certain windows can not be set for a light gray background.

-- Eric K3NA

-----Original Message-----
From: writelog-bounces at contesting.com
[mailto:writelog-bounces at contesting.com]On Behalf Of Richard Zalewski
Sent: 2003 February 23 Sun 15:05
To: Georgek5kg at aol.com
Cc: fcg at mailman.qth.net; writelog at contesting.com
Subject: [WriteLog] Re: Check Call Window - OK?


George,

Like your proposal for red and green.  As soon as that is thrown out though there will be someone who is using a monochrome monitor
somewhere.  Anyway good idea and I too do not like the empty call window filled with OKs.

Dick W7ZR

  ----- Original Message -----
  From: Georgek5kg at aol.com
  To: w7zr at citlink.net
  Cc: writelog at CONTESTING.COM ; fcg at mailman.qth.net
  Sent: Sunday, February 23, 2003 10:04 AM
  Subject: Check Call Window - OK?


  In a message dated 2/23/2003 4:04:06 PM Greenwich Standard Time, w7zr at citlink.net writes:


    Like XXX in
    red replacing OK, or Worked in red ...


  Dick,

  Funny you should mention the "OK", as I had a guest op in ARRL DX who was new to WL and went the entire contest not realizing its
significance!

  "OK" in the Check Call Window has always made sense to me as meaning "this mult has been worked on this band".  However, I do
understand, that "OK" can mean different things to different operators.  Terms like "OK" are pretty loose and open to
interpretation.

  What I don't like is for the Check Call Window to initially show "OK" on all bands when there is no entry in the QSO Entry Window.
Now that is confusing to me.  I would prefer the Check Call Window to initially show only the "Bands" without an OK, and then pop up
the "OK" on the appropriate bands when the mult's prefix is entered [as it does].

  To comment on your suggestions:

  1.) using "XXX" in red instead of OK...to me this would be even more confusing than using OK.  Again, loose and non-specific.

  2.) using "Worked" in red would be good, except that it would take more space than "OK".  And space in this window is at a real
premium, especially if you have the Band Map open.

  Here is my proposed solution:  In the Check Call Window, have the Bands appear in Red and Green, indicating whether or not the
multiplier is needed on that band.  This would eliminate the "OK" altogether and save space..  As with mults in the Packet Spots
Window, use color to "manage by exception".  Now there is an IDEA for Wayne to consider!

  Thoughts?

  73, Geo...

  George I. Wagner, K5KG
  Productivity Resources LLC
  941-312-9450
  941-312-9460 fax
  201-415-6044 cell



_______________________________________________
WriteLog mailing list
WriteLog at contesting.com
http://lists.contesting.com/mailman/listinfo/writelog




More information about the WriteLog mailing list