[WT-support] WT 3.10.0

Dave Zeph zephd at indy.rr.com
Thu Mar 22 22:47:20 CET 2007 

You need to read the parts about SEGMENTS, and MARKERS carefully.

Also decide whether you want to display the QSO NUMBER or not.

One thing that came to mind when I looked at the Display with QSO NUMBER
turned off is that the two choices on COLUMN ALIGNMENTS are:

1) Centered
2) Left Aligned

Take a look at the display and tell me if what's missing is a RIGHT
ALIGNMENT option???  I would use RIGHT ALIGNED if it were available.

Another case of FROG brain and GERMAN/IRISH brains working out-of-phase!!!
But seriously, tell me what you think.




---- Dave



> -----Original Message-----
> From: support-bounces at win-test.com [mailto:support-bounces at win-test.com]
> On Behalf Of Olivier F5MZN
> Sent: Thursday, 22 March, 2007 17:23
> To: WT
> Subject: [WT-support] WT 3.10.0
> 
> Dear fellow WT users,
> 
> WT 3.10.0 is out:
> http://download.win-test.com/wt-3.10.0.exe [full, 4MB]
> http://download.win-test.com/wt-3.10.0-update.exe [update only, 2.3 MB]
> 
> This version comes with a feature needed by some requests regarding the
> WPX. The serial number is now separated by half a space char to the
> report. It is also possible to hide the total QSO number. That is just
> the emergency improvements done before the WPX SSB. Please read the
> following release information to lurn more about this version.
> 
> Good luck in the coming WPX!
> 
> Release 3.10.0 (Mar 22, 2007)
> -----------------------------
> 
> - Bugfix: $TR1 and $TR2 macros were not working using the microHam
>    MK2R interface. Fixed. Tks OH2UA.
> 
> - New tool : Time shifting, in the Tools menu.
> 
>    You can time shift selected Qsos by any amount of time amount in both
>    directions. You can apply the time shift for the entire log, for the
>    Qso entered by your own station, for Qso entered by several stns,
>    or a range of Qsos.
> 
>    Even if this tool is more supposed to be used after a contest,
>    to correct a wrong clock setting, each time corrections is
>    broadcasted to the other stns of the network by default. You can
>    disable this broadcasting to save time, if not needed.
> 
>    Note that time shifting is pretty CPU intensive and it may take
>    a certain amount of time for large logs, because each Qso
>    modification requires internal structures (mainly statistics) to be
>    updated.
> 
>    Note : Hesitating and wise users are encouraged to perform a backup
>    of their log before proceeding. Time shifting can't be cancelled
>    while it is in progress, to avoid any log inconsistancy..
> 
> - Main log window : New option in Options / Log menu to hide the QSO
>    number column. Tnx RW3AH, SM3WMV.
> 
> - Main log and secondary radio windows : To ease reading, the received
>    RS(T) and the received exchange are now separated by an half space
>    wide blank area.
> 
>    Note that it is still *one unique* field. It is only a display trick.
> 
> - New feature : Band segments for bandmaps
> 
>    You can now display segments in the bandmap tab of the radio
>    windows. Segments are defined by textual files with a .seg extension
>    located in the Win-Test directory. You can use and display up
>    to 10 files simultaneously, by selecting them in the Options /
>    Data files / Segments files... menu.
> 
>    Note that, because of the available area constraints, you can't have
>    more than 5 segments displayed per band for a given frequency.
> 
>    You can display or not the loaded segments by using the contextual
>    menu item Display Options / Segments / Display. This setting can be
>    different for each radio.
> 
>    The syntax of the segments files is very basic, and are very easy
>    to create with a simple text editor like notepad.
> 
>    A segment is defined by its miniumum frequency (in kHz), its maximum
>    frequency (in kHz) and an optional tooltip (30 chars max.). The two
>    frequencies can be linked by an hyphen.
> 
>    Example :
> 
>    14150-14350 Extra licences SSB
> 
>    A directive is also allowed :
> 
>    # COLOR color => Set the color of the following segments of the file
> 
>    The allowed colors are :
> 
>    White, Black, Red, Green, Blue, Yellow, Magenta, Cyan.
> 
>    The case of the color is irrelevant. If no color is specified, the
>    segments will be yellow.
> 
>    Example :
> 
>    # COLOR blue
>    #
>    14150-14350 Extra licences SSB
> 
>    will display this segment in blue on the bandmap. Its associated
>    tooltip will be "Extra licences SSB".
> 
>    The segments order, and potential overlaps in the file are irrelevant.
>    WT will take care to display them in an optimized way.
> 
>    Two sample files are located in our repository :
> 
>    http://download.win-test.com/files/segments/
> 
>    UsSegmentsDetailled.seg displays all band segments for every US
>    licence type.
> 
>    UsSegments.seg displays all band segments in which all US licencees
>    are potentially active.
> 
>    You can make your own band segments files for other countries,
>    regions, etc. and share them with the WT community if you want.
> 
>    Tnx DL1MGB for inspiration.
> 
> - New feature : Markers for bandmaps.
> 
>    You can now display markers in the bandmap tab of the radio
>    windows. Markers are defined by textual files with a .mkr extension
>    located in the Win-Test directory. You can use and display up
>    to 10 files simultaneously, by selecting them in the Options /
>    Data files / Markers files... menu.
> 
>    You can display or not the loaded markers by using the contextual
>    menu item Display Options / Markers / Display. This setting can be
>    different for each radio.
> 
>    The syntax of the markers files is very basic, and are very easy
>    to create with a simple text editor like notepad.
> 
>    A marker is defined by its frequency (in kHz), its label (one word)
>    and an optional tooltip (30 chars max.).
> 
>    Example :
> 
>    14100 Bcn NCDXC Beacon
> 
>    Two directives are also allowed :
> 
>    # BACKGROUND color => Sets the bg color of the following markers of
>    the file. If no color is specified, the default color is green.
>    # TEXT color => Sets the text color of the following markers of the
>    file. If no color is specified, the default color is.black
> 
>    The allowed colors are :
> 
>    White, Black, Red, Green, Blue, Yellow, Magenta, Cyan.
> 
>    The case of the color is irrelevant.
> 
>    Example :
> 
>    # BACKGROUND white
>    # TEXT green
>    #
>    14100 Bcn NCDXF Beacon
> 
>    will display a white marker with "Bcn" green text. The associated
>    tooltip will be "NCDXF Beacon".
> 
>    As usual, you can double-click on a marker to set the current
>    radio on the freq. of the marker.
> 
>    A sample file is located in our repository :
> 
>    http://download.win-test.com/files/markers/
> 
>    called NcdxfBeacons.mkr. It displays markers for each NCDXF beacon.
> 
>    You can build your own markers files (VHF beacons etc.) and share it
>    with the WT community if you want.
> 
>    Tnx DL1MGB for inspiration.
> 
> - WPX contest : Mult wnd (Alt-M). Band selection menu item removed.
>    It also applies for the RDAC contest. Tnx I4UFH.
> 
> 73,
> --
> olivier / f5mzn
> _______________________________________________
> Support mailing list
> Support at win-test.com
> http://www.f5mzn.org/cgi-bin/mailman/listinfo/support

More information about the Support mailing list