JT65-HF now released (ver. 1.0.9)

Newest version of JT65-HF now released (ver. 1.0.9) - get it here:

JT65-HF ver. 1.0.9

Changes to version 1.0.9

• Operator's call-sign and grid must be valid for use with JT65 Protocol. If not transmit will be disabled. This will also impact the (few) stations using SWL call-signs as those will not validate.
• New message parser and generator code. Message parsing is now more strict in what “it” considers as a valid exchange. In some cases decodes that would generate a message inprevious versions will not in 1.0.9.
• New RB code. The RB code has been completely overhauled on both the server and client side – this will have little impact on end users other than no longer spotting certain nonstandard messages that previously spotted (often with error).
• Removed small GUI version. In its place the program is now resize-able to a minimum height of 550 pixels. This should accommodate small screens found on some Net-books, but, 550 pixels vertical height is an absolute minimum height. The horizontal resolution remains locked at 935 pixels.
• Added line to separate decode periods in decoder text output area. The separator line will not display if you have a small vertical height.
• Log window now contains option to clear notes field at each showing of window or not. Any text in the notes field is also saved to configuration file in case you wish to use a persistent text for it.
• Increased user defined QRG and macro spaces.
• Deleted all WARC band frequencies from predefined (hard-coded) menu. In practical terms there are only three bands where there is no (or very little) contention over correct frequency – those being 20, 15 and 10 meters. In the case of 40 and 80 meters there is contention with the “standard” frequencies but not so much as to warrant removal of them as promoted values. For the WARC bands there is absolutely no agreement on a good value set that works for the entire world, so, I have decided to get out of the mess by letting the users decide without my input where to operate on those bands. An imperfect solution at best, but, until things change in this regard it will remain the solution of choice.
• Many bugs fixes.
• Fixed issues with local settings for decimal and thousands separators. The code should now work regards of your chosen characters for those items. Forcing Unicode strings so Cyrillic characters (and – potentially – other extended types) now display properly. Mainly applies to sound device selectors.
• Divider line in decoder output area will be optional.  If you like it you can keep it on, if not you can turn it off.  :)
• Restored text indicating the Current Action program is working on.
• Moved Answer CQ and Send Report buttons back to their "traditional" right justified positions.
• Corrected issue with CW ID being truncated.  When sending CW ID the entire text will either be sent or nothing will be sent if it's too long to finish before start of new period.
• Added option to only send CW ID when sending Free Text versus current method of sending with free text OR 73 message.
• Changing late start TX such that TX tones begin where they would have had the TX started on time.  May take a bit of thinking to see why this is a good thing, but -- it is.  :) Look at it this way... if you started TX on time but a fade took out the first x seconds from the RX point of view you might still get a decode and the DT wouldn't be reported as in error as the timing is correct even if a "piece" is missing.  The current code begins at the normal start point but not the normal start time leading to DT error if the RX station can decode the late start TX at all.  This change should improve the odds of getting decodes from a late start TX.

As far as I can tell this update will not require an updated JT-Alert, but, Laurie will be the ultimate confirmation point for that. This can be considered an optional update as it is not necessary unless one of the changes listed above is of interest to you.

73 - Joe - W6CQZ