From what I can see, there are two "BLUE" selections that MAY NOT be checked.

Scroll that window, or drag the windows a bit larger, and you should the see the 'New Call' and 'New Call in Band'  checkboxes and colors.   Select those two,  and you'll then have new callsigns in a shade of blue.   You can also do what I did was 'uncheck' the CQ in message line, so that stations calling CQ that I've worked before will not display in any color.

Neil, KN3ILZ

On 12/15/2018 5:37 PM, L Barley wrote:
image.png

Sorry, the worked before status I was looking for was that the station calling CQ in the band activity widow would change color after I had a QSO with them.

TU
Lance
KD4FW

On Sat, Dec 15, 2018 at 5:14 PM Neil Zampella <ne...@techie.com <mailto:ne...@techie.com>> wrote:

    All that's left is a screen capture of the colors window so we can
    see what is setup there.

    Neil, KN3ILZ

    On 12/15/2018 5:02 PM, L Barley wrote:
    Alrighty then....both the wsjt_log.adi and the all.txt files are
    present and accounted for.  I opened the all.txt file in notepad
    and it appears to be in order, so I'm apparently not well and
    truly stuffed....I hope.

    I've saved the preferences both with and without the *Show DXCC,
    grid, and worked-before status* box checked in the
    Settings/General tab with no change.  I would do the following: 
    Save Preferences / Close program / Reboot computer / Open program.

    I've also tried different combinations of selections in the
    Settings/Colors tab varying from all selected to none selected. 
    My selections on that tab that I use are: "My Call in message",
    "CQ in message" and "Transmitted message".  They are currently in
    that order of priority from highest to lowest.

    I've also used the "Rescan ADIF Log" from the Settings/Colors tab
    to see if it would manually pick up the worked before information
    with no change.....

    I've uninstalled all the older versions of WJST-X that were
    lurking around as well as uninstalled and re-installed v2.0.0.  I
    then went through the Save Preferences drill as described above
    as well as the various Settings/Color tab selections and "Rescan
    ADIF Log" with a "fresh" install and still no change in the
    worked before status....?

    Thanks for the help...

    GL 73
    Lance
    KD4FW

    On Sat, Dec 15, 2018 at 3:55 PM Gary Hinson <g...@isect.com
    <mailto:g...@isect.com>> wrote:

        Hi Lance.

        Since you weren’t explicit about those ‘appropriate boxes in
        the settings area’ but you’ve been working on it for days, I
        guess you either know what you are doing there or have hit
        all possible combinations … but there’s another factor you
        didn’t mention.  The worked-before function uses QSO details
        saved in the ADIF log file stored in the WSJT-X log folder. 
        The ADIF log file is read into memory when WSJT-X launches.

        Have you, perhaps, deleted, renamed or mysteriously
        lost/corrupted your stored ADIF log?

        If so, you’ll need to replace, repair or regenerate it e.g.
        from a backup, or an ADIF export from your logging program,
        or a Club Log or LoTW or QRZ logbook download, or checking it
        manually in a text editor, or manually recreating the
        essentials of by poring through your ALL.TXT QSO-by-QSO and
        generating a replacement ADIF log (assuming you haven’t
        /also/ lost your ALL.TXT file, in which case you’re stuffed
        mate).

        73
        Gary  ZL2iFB

        *From:* L Barley <kd4fw.f...@gmail.com
        <mailto:kd4fw.f...@gmail.com>>
        *Sent:* 16 December 2018 09:19
        *To:* wsjt-devel@lists.sourceforge.net
        <mailto:wsjt-devel@lists.sourceforge.net>
        *Subject:* [wsjt-devel] worked before status

        I'm using v2.0.0 on Windows 10 and the "worked before status"
        isn't functioning.  It looks like I have the appropriate
        boxes selected in the settings area.  I've been working on
        this for several days without any improvements.....

        Does anyone else have this issue?  Is there a fix for this?

        Thanks.

        Lance

        KD4FW

        _______________________________________________
        wsjt-devel mailing list
        wsjt-devel@lists.sourceforge.net
        <mailto:wsjt-devel@lists.sourceforge.net>
        https://lists.sourceforge.net/lists/listinfo/wsjt-devel


    
<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
        Virus-free. www.avg.com
    
<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>


    <#m_1999809206658020912_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
    _______________________________________________
    wsjt-devel mailing list
    wsjt-devel@lists.sourceforge.net
    <mailto:wsjt-devel@lists.sourceforge.net>
    https://lists.sourceforge.net/lists/listinfo/wsjt-devel



---
This email has been checked for viruses by AVG.
https://www.avg.com
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Reply via email to