Just some further clarification on what I would like to see:
An option, to have the Writelog place the focus back on the log screen callsign
entry field when Writelog is doing a Timed CQ (Auto CQ). I thought further
about a timer that would send you back there no matter what was going on, but I
don't think that would work. The key to this, is that you're doing a Timed CQ.
The way this would work, is that when the CQ message completes, put the focus
back to the main log Window so that you could begin logging if someone calls.
Now, this might get annoying if you really want to do something else. Well -
then stop the Timed CQing while you go do something else, or shut this option
off.
For me, while I'm operating, I always want to log the guy calling me, and
nothing is more important than that, so I would always want the program to
force me back to the callsign entry field at the end of each CQ.
While a single key would be cool, I still see that as a panic mode rather than
automatic. I prefer automatic.
N5NJ
> ------------Original Message------------
> From: "W. Wright, W5XD" <w5xd@writelog.com>
> To: <writelog@contesting.com>
> Date: Mon, Dec-15-2003 9:51 PM
> Subject: RE: [WriteLog] Re: issues--HOME key
>
> >
> > Now, there's a good idea !!...I vote for this...HOME key has no other
> > use....I can never remember all the CTRL/ALT stuff when I'm
> > in a pileup...
> >
> > How about it Wayne ? Possible ?
> >
>
> Here is the problem: "HOME key has no other use". That might or might
> not be true depending on whether you are using it the way it is supported
> in the program right now. If the keyboard focus in in the Entry window,
> then HOME (and END) move the cursor to the beginning and end of the
> current field (like happens in pretty much any Windows text editing
> control).
>
> If the keyboard focus is in the log window, HOME and END scroll the
> log to the first and last QSO in the log.
>
> The first function is not a conflict with what is being proposed by this
> thread. The second function (scrolling the log window) is a conflict,
> and, in order to make WL do what is being asked, the old behavior
> would be lost. Experience tells me not to jump into changes without
> first being sure that the request is really coming from the majority
> and not a vocal minority--it is even more painful to have new releases
> change the behavior back after protests with a new one.
>
> So I am going to sit on this one for a bit and see if anyone chimes in.
> Wayne
> _______________________________________________
> WriteLog mailing list
> WriteLog@contesting.com
> http://lists.contesting.com/mailman/listinfo/writelog
> WriteLog on the web: http://www.writelog.com/
>
_______________________________________________
WriteLog mailing list
WriteLog@contesting.com
http://lists.contesting.com/mailman/listinfo/writelog
WriteLog on the web: http://www.writelog.com/
|