[WriteLog] Newbie observations (from the ex TR user)

[Bruce Ferry]

Thanks to all who have responded! Some good things did come from the 
responses and next contest (I think the RAC Winter Contest) will go 
smoother.

I had several suggestions to use F11 (after an INI file change) to clear 
the duplicate call. This would be better but it's still not what I want. 
For best operation during the contest the duplicate QSO needs to clear 
automatically. I know this isn't what everyone would like so could it be 
an option?

Some good hints about window placement tinkering are found on W9JY's 
site ( http://www.k9jy.com/ ) and this helps but I've found out that 
only by actually doing it (over and over) will you get a feel for how it 
works. One of my major restrictions is the laptop is 800x600 and this 
does limit what you can do.

I had run through W9JY's site some before but I see I have to actually 
go through it in detail to glean everything there. Such a wealth of 
information!

My problem with window position being remembered applies only to some of 
the windows. Saving the configuration does nail down most of them but 
not all. I think I've seen other people talking about this too so it's 
not something I seem to be doing wrong.

Bruce Ferry wrote:
> I ran the 10 M contest with the shiny new WL 10.37b. Coming from the TR 
> world, here are my observations.
> 
> 1. Writelog flawlessly read my radio - something TR has trouble doing on 
> a consistent basis (no, it's not RF - it happens while receiving only). 
> This is the primary reason I looked at Writelog in the first place so 
> I'm happy here.
> 
> 2. I found it annoying to have to manually clear the QSO entry window 
> whenever I had a duplicate. This is something TR does much better in my 
> opinion. Having to do ALT-W or CTRL-BKSP to clear stuff out put undue 
> strain on my poor fingers and kept me looking at the keyboard all the 
> time. I would REALLY like the option of clearing the QSO data 
> automatically if it's a duplicate.
> 
> 3. I found the bandmap a super aid. I found myself looking at the 
> bandmap instead of the radio to see where I was on the dial. I don't use 
>  Packet (unless it doesn't matter) in contests so what went on the 
> bandmap was only what I put there. I eventually entered every call (and 
> hit the spacebar) for everything I heard so I would see it on the 
> bandmap and not waste my time listening for the call. This isn't perfect 
>  (sometimes the owner of the frequency changes) but it did help. Item #2 
> above made this harder than it should have been.
> 
> 4. I was very frustrated trying to get a reasonable window layout. WL 
> just refuses to let me put anything above or below the QSO entry window 
> even if it would fit physically. There seems to be some odd restrictions 
> that don't seem to make any sense to me.
> 
> 5. I really miss the score at least being SOMEWHERE on the screen even 
> if you don't display the band summary. I use a laptop for the actual 
> logging computer but since there is another computer right at hand I 
> just networked them together and showed the band summary and rate window 
> on that one. It turned out to be a usable solution with a bit of 
> redundancy - which I fortunately didn't need.
> 
> 6. I also found that the lack of "memory" about where windows are placed 
> annoying. The multiplier window in particular.
> 
> 7. I don't mind tinkering with INI files but a comprehensive guide to 
> EVERYTHING in the INI file would help a lot.
> 
> -- 
> Bruce Ferry, AK8B
> 
> _______________________________________________
> WriteLog mailing list
> WriteLog@contesting.com
> http://lists.contesting.com/mailman/listinfo/writelog
> 
> 

-- 
Bruce Ferry, AK8B