Number Description Version corrected 1 clicking the Rcv or Xmit buttons in the Soundcard Levels panel causes some systems to crash 1.1 2 crashes or fails to load on a 90 mHz Pentium with 32mb RAM 1.5.1 3 incorrectly reports the absence of PSKCore.DLL 1.1 4 crashes when > precedes < in a macro definition 1.3.1 5 crashes when temporary files cannot be created 1.3 6 tab order is reversed on the function key macro definition screen 1.5.6 7 broken hyperlinks in online help 1.5 8 can't switch windows with <ALT><TAB> if WinWarbler is on top 9 can't send line breaks in version 1.5.9 1.6.0 10 can't select callsigns containing a Ø 1.6.7 11 selecting callsign, name, report, and QTH is unreliable when running under Windows 2000 1.6.7 12 / in callsign causes program termination on minilog creation 1.6.8 13 insufficient precision in RX frequency causes inaccurate Hz. digit 1.7.2 14 panel ID not properly repainted after change of font color 1.7.9 15 incoming backspace characters improperly handled 1.7.9 16 centering 2 decimal points in the "xcvr freq" text box causes crash 1.8.0 17 if a receive pane is made to disappear, it cannot be made to re-appear 1.8.0 18 transmit pane font color is not saved between sessions 1.8.1 19 starting transmission within ~250 ms. of switching panes can select the previous pane's net transmit frequency 1.8.5 20 WinWarbler versions beginning with 1.8.1 improperly compute UTC dates in the year 2001 -- an erroneous 2 days are added, so that 1-Jan-2000 is reported as 3-Jan-2000 1.9.2 21 Date in header of mini-log export file contains incorrect year 1.9.4 22 Runtime error 380 when run on Windows 2000 SR1 (build 2195) with Italian locale 23 Soundcard RTTY (MMTTY) squelch control is inoperative 2.0.1 24 clicking on receive pane clears waterfall display 2.0.2 25 unreliable interoperation with Commander 2.0.2 26 MMTTY fails to start on some systems 2.0.9 27 frequency scale is not displayed when xcvr frequency is < 4 khz 2.0.7 28 RTTY modem window color coding of received vs. transmitted characters is incorrect 2.0.9 29 clicking the RTTY receive pane's OPT button causes a runtime error if an offset has not been specified 2.1.0 30 PTT for soundcard RTTY not reliably initialized 2.1.5 31 soundcard RTTY XY display not reliably initialized 2.1.5 32 RX and TX frequencies above 100 mhz are improperly displayed 2.1.7 33 RTTY receive panel and AutoArchive directory creation errors introduced in 2.2.6 2.2.7 34 KAM doesn't return to CMD mode after RTTY mode is terminated 2.3.0 35 sats label on main window should not be visible unless GPS is enabled 2.3.3 36 gracefully recover from window positioning errors 2.3.3 37 Config window's Display tab doesn't display font colors after program startup 2.3.4 38 With PTT Mode set to RTS+DTR, switching from PSK to soundcard RTTY generates a "unable to open PSK PTT serial port" message 2.3.8 39 enabling or disabling Soundcard RTTY mode during PSK operation disables the waterfall and frequency displays 2.3.5 40 version 2.3.6 can't be shutdown by the DXLab Launcher 2.3.7 41 when directed by SpotCollector to set a RTTY frequency, version 2.3.6 fails to do so if neither soundcard RTTY nor external RTTY modem are enabled 2.3.7 42 changes to a macro definition are not reflected in its tooltip (popup) 2.3.9 43 macros that include line breaks aren't fully displayed in the transmit pane after activation 2.3.9 44 soundcard overload indicator fires after transition from transmission to reception 2.3.9 45 changing frequency doesn't set the band control 2.4.0 46 treat an incoming Ø as zero when decoding callsigns 2.4.0 47 tolerate non-numeric RTTY offsets without generating an errorlog entry 2.4.0 48 correct explanatory Transmit Pane popups in the Config window's Display tab 2.4.1 49 don't overwrite QSO Info data if DXKeeper is running but the RAC callbook is disabled or not installed 2.4.3 50 if radio mode is USB, switching to a RTTY channel configured to AFSK(LSB) doesn't change the mode to LSB 2.4.5 51 initialize and save the Waterfall color settings for Soundcard RTTY operation 2.4.8 52 Expect the locale's decimal separator character in fields that accept decimal numeric values 2.4.8 53 <clear_qso> macro command doesn't clear DXKeeper's Capture window 2.5.0 54 when switching from soundcard RTTY to PSK, check to see if soundcard has been released by the MMTTY engine; if not, wait until its available before beginning PSK operation 2.5.1 55 correct receive pane initialization error that sometimes occurs when switching from PSK to RTTY 2.5.2 56 eliminate flicker when attempting to resize the main window to less than its minimum height or width 2.5.2 57 soundcard RTTY trace width control is inoperative 2.5.4 58 clicking the QSL Info panel's Log button doesn't clear DXKeeper's Capture window 2.5.4 59 clicking theTransmit PSK panel's CWID button fails to activate the transmit pane, so subsequent keystrokes -- data or function keys -- are ignored until the user manually clicks in the transmit pane 2.5.4 60 the "Set Default Color" function does not save the default trace color (used to render spectrum, vector, and XY displays) between sessions 2.5.5 61 opening the multiline macroeditor fails if it had previously been minimized 2.5.6 62 the Enter key should function in soundcard and external RTTY whether or not the "Send control characters from Transmit Pane" box is checked 2.5.7 63 the Optimal Offset command does not work correctly with Soundcard RTTY 2.5.8 64 missing or incorrect tooltips for various Config settings 2.5.9 65 if started in soundcard RTTY mode, the first switch to a PSK mode and the subsequent switch back to soundcard RTTY mode don't function correctly 2.6.3 66 CW identification speeds in PSK63 mode are incorrect 2.6.3 67 set focus to Transmit pane after closing the Config or Macro Editor windows so that function keys can be used 2.6.4 68 retain Doppler-tracking AFC setting between sessions 2.6.4 69 accept information from remote QSO lookup and/or Callbook lookup whether the Callbook is enabled or not 2.6.6 70 correct error in implementation of Dual Monitor support 2.6.6 71 remember between sessions whether the QSO Info panel's Notes or QSLMsg is to be displayed 2.6.7 72 failure to properly shut down on some systems 2.6.8 73 <LastQSO> macro's frequency is improperly formatted on some systems 2.7.4 74 PSK AFC label is depicted in the wrong font 2.6.9 75 extraneous "QSLRequest" label is visible 2.6.9 76 after initiating macro editing by Ctrl-Clicking a macro button, macros can't be initiated via Function key until they are first imitiated by a mouse click 2.7.0 77 ensure that horizontal zoom can't be set to 0 2.7.1 78 clicking in horizontal pan slider background doesn't update frequency display 2.7.1 79 when operating soundcard PSK or RTTY in LSB, ensure that the transceiver frequency is no lower than 4khz 2.7.3 80 CTRL-clicking a macro button to initiate editing should not execute the macro (regression introduced in 2.7.0) 2.7.4 81 setting receive and transmit frequencies by clicking in the waterfall display in LSB mode with zoom >1 did not work correctly 2.7.4 82 click the Stop button in the PSK Transmit or RTTY Transmit panel does not clear the Transmit pane 2.7.5 83 clicking on the PSK panel's AFC label won't toggle the doppler AFC if WinWarbler starts up with AFC set to 0 2.7.6 84 the first previous QSO check after WinWarbler starts doesn't update the Call label to indicate the number of previous QSOs 2.7.6 85 <lastqso> macro repeats the word "our" 2.7.7 86 AFSK RTTY Mark Offset implemented incorrectly for non-zero values 2.8.0 87 striking F10 or ALT-F10 loses keyboard focus until F10 is struck a second time 2.8.2 88 reimplement RTTY Mark offsets so that the same offset works on both LSB and USB 2.8.4 89 move RTTY Mark Offset settings to the Soundcard RTTY tab (since they only apply to Soundcard RTTY operation) 2.8.4 90 PSK offset applies to transmit as well as receive frequencies 2.8.4 91 Transmit from Clipboard and Transmit from File don't work in RTTY 2.8.4 92 use MHz rather than mHz in the <LastQSO> macro 2.8.5 93 eliminate unnecessary transceiver control directives at startup 2.8.6 94 if the PTT mode is set to "Xcvr Ctrl SW" and Soundcard RTTY modulation is set to AFSK, then MMTTY is directed to not open a serial port if the PTT mode is set to "Xcvr Ctrl SW" and Soundcard RTTY modulation is set to FSK, then MMTTY is directed to open the specified serial port (so that its TXD signal can be used to drive a level converter connected to the transceiver's RTTY input)
2.8.6 95 error in calculation of monitor channel display width 2.8.7 96 monitor channel display does not re-appear when switching from RTTY to PSK 2.8.8 97 Waterfall display defect when run with a Finnish locale 2.8.9 98 don't allow monitor channel window to appear unless mode is PSK31 or PSK63 2.8.9 99 retry DDE Log operations 3 times before giving up 2.9.1 100 ensure that receive pane triangles are visible atop monitor channel triangles above the waterfall 2.9.1 101 Channel Monitor window doesn't resize the channel display when maximized 2.9.2 102 reset unlocked channels every 2 seconds rather than every 200 ms 2.9.2 103 eliminate the frequency marker display when the channel monitor is disabled and the tuning display ID is set to traces 2.9.3 104 monitor channel frequencies don't take the PSK offset into account 2.9.3 105 with Broadband Decode enabled, CPU consumption becomes 100% on some PCs 2.9.4 106 double-clicking on a PSK Spot Database Entry fails to place the transceiver into the specified mode if WinWarbler was already in PSK and the specified mode is not SSB 2.9.5 107 if main window is minimized when double-clicking on a PSK or RTTY spot in SpotCollector, WinWarbler fails to appropriately reconfigure its window 2.9.7 108 eliminate unnecessary transceiver mode changes during initialization and shutdown 2.9.8 109 clearing the transmit pane via its right-click menu entry while in PSK31 or PSK63 mode should clear PSKCORE's transmit buffer 2.9.9 110 changing the transmit pane font color should alter any characters already in the pane 2.9.9 111 can fail to remove an overage entry from the Station Heard window under certain circumstances 3.0.0 112 closing the Monitor window can generate an errorlog.txt entry 3.0.1 113 clicking the Station Heard window's X button should minimize it, rather than close it 3.0.2 114 changing a macro button's font or face color may not take effect until you change the Main window's Alt checkbox twice 3.0.2 115 before a new profile is established, remember the AFC, BPF, reverse transmit/receive, and unshift on space settings; after the profile is established, restore those settings 3.0.2 116 triangle frequency designators flicker 3.0.5 117 selected PTT port is opened even if PTT mode is set to "none" 118 Channel Monitor window entries flicker 119 in the Stations Heard window, changing column widths followed by changing data column width followed by resizing windows causes unexpected results 3.0.6 120 double-clicking on the first-letter of a callsign fails to capture it 3.0.6 121 <xcvrsequence> macro doesn't handle sequence numbers 8 through 15 3.0.7 122 executing a macro resets Keyboard Pane to black font 3.0.7 123 CW offset isn't saved between sessions 3.0.8 124 "WinWarblerMain.QSLRequested_Click: Invalid procedure call or argument" errorlog entry on startup 3.0.8 125 If WW is in RTTY mode, double clicking on a CW spot in WW does not change the rig to CW 3.0.8 126 striking a macro button while transmitting in CW causes a glitch in CW generation 3.0.8 127 when in CW mode, don't interpret Enter or Newline as character spaces 3.0.9 128 eliminate errorlog.txt entries generated when tuning display height is set to 0 3.1.0 129 when receiving a frequency and mode from SpotCollector with "Contest Mode" or "Preset RST fields to 59/599" checked, don't set the QSO's start time 3.1.1 130 correct tooltip errors and omissions 3.1.2 131 support PTT via selected serial port 3.1.3 132 eliminate loss of DDE connectivity with Commander when using Commander for PTT with a lag time of 2-6 ms 3.1.4 133 save the soundcard/modem receive pane layout between operating sessions 3.1.5 134 switching to RTTY with Commander running doesn't properly update the transceiver mode 3.1.6 135 main window size for RTTY and/or PSK operation is not preserved between sessions if WinWarbler is shut down in CW or phone mode 3.1.6 136 Transmit from file is not functional in CW mode 3.1.8 137 When the External Modem tab's "Send control characters from Transmit Pane" box is checked, control character struck in the Transmit Pane other than CTRL-J, CTLR-Q, CTRL-R, CTRL-S, and CTRL-V should be sent to the External Modem, not interpreted as keyboard shortcuts for navigation in the QSO Info panel 3.1.8 138 Control characters other than CTLR-Q, CTRL-R, and CTRL-S (<17>, <18>, and <19>) contained in macros are conveyed to the external modem if in CW mode with keying via the external modem, or if in RTTY mode with the external modem's receive pane active 3.1.8 139 don't send MMTTY a stop-when-empty message if transmission is not in progress; instead, wait for the next transmission and send the stop-when-empty message after sending the first character 3.1.9 140 when shifting from PSK to RTTY with both soundcard RTTY and the external modem enabled, allocate the third receive pane's space pro-rata to the soundcard RTTY and external modem receive panes 3.2.0 141 when CW AutoStart and CW AutoStop are disabled because the Send control characters from Transmit Pane setting is checked while in CW mode with keying via the external modem, remember there previous values and restore them when the Send control characters from Transmit Pane setting is unchecked or CW keying is set to something other than external modem or the mode is changed to something other than CW 3.2.0 142 don't close the external modem port when switching from CW via external modem to RTTY via external modem 3.2.1 143 when presented with a callsign by SpotCollector, don't direct DXKeeper to filter the Log Page Display 3.2.3 144 clearing the QSO Info panel should update the panel's caption to show no start time 3.2.4 145 when switching from soundcard RTTY to PSK with PTT mode set to 'none', WW incorrectly waits for MMTTY to release the PTT port 3.2.4 146 if operating soundcard PSK or RTTY in LSB without Commander, the Xcvr Freq control can become "stuck" at 4 3.2.6 147 Receive frequency isn't properly initialized when switching to Phone mode 3.2.6 148 Use 10mHz to choose between USB and LSB 3.2.6 149 if Commander is not running, initialize WInWarbler to the mode in use during the previous session 3.2.7 150 properly set Main window size at startup when transceiver mode results in a mode different from that of the last operating session 3.2.7 151 Help button on the Config window's CW/Phone tab is inoperative 3.2.8 152 Display font metrics are sometimes not accurately preserved between operating sessions due to font size rounding 3.3.1 153 WinWarbler Macros window doesn't fit on an SVGA display 3.3.2 154 errorlog.txt entries reporting overflows in PhoneXcvr.NewXcvrMode and PhoneXcvr.UpdateReceiverFreq 3.3.2 155 if a reasonable startup mode can't be determined, start in Phone Mode rather than generate an errorlog.txt entry 3.3.2 156 eliminate errorlog.txt entry generated by WinWarblerMacros.UpdateBankCaption 3.3.3 157 when expanding or contracting the QSO Info panel, expand or contract the Main window size to match 3.3.5 158 provide a reasonable tab order within the Main window's QSO info panel 3.3.5 159 Main window height is improperly initialized in CW and Phone mode (regression introduced in 3.3.3) 3.3.6 160 Alt-shortcut keys should not select the primary macro bank 3.3.6 161 ensure the correct vertical spacing when switching between modes 3.3.7 162 handle longer soundcard product names 3.3.7 163 if a <loadmacrobank> or <savemacrobank> macro is executed without a <macrobank> macro having first established which macro bank to load or save, macro bank 1 is assumed 3.3.8 164 ensure that unused receive panes (0 and 2 in CW, 2 in RTTY) never appear, and disable the splitter bars that would enable them to be made visible 3.3.8 165 the TX# field ignores Alt-Nav shortcuts 3.3.8 166 ALT-U should not select the primary macro bank 3.3.8 167 Striking a key in the Freq selector should not move the cursor focus to the transmit pane 3.3.9 168 Use Alt-/ rather than Alt-M as shortcut to the Transmit pane 3.3.9 169 QSO Info's RST Sent label is misplaced 3.4.0 170 when the user double-clicks on a SpotCollector Spot Database Entry with DXKeeper running, only update the QSO Info panel with previous QSO and Callbook information if the Auto Lookup option is enabled and if SpotCollector is configured for WinWarbler handle the spotted station 3.4.0 171 hide vestigial receive panes and panel ids 3.4.0 172 ensure the phone QSOs use the QSO Info associated with receive pane 0 3.4.0 173 refuse to log a QSO whose callsign can't be mapped to a DXCC entity 3.4.1 174 accept expanded spot information in DDE command from SpotCollector and use it to generate outgoing DDE Commands to DXKeeper and Pathfinder (rather than let SpotCollector do this, which caused a race condition) 3.4.1 175 not exporting RX frequency via DDE in CW and Phone mode 3.4.1 176 striking Enter in the Callsign field, double-clicking the Callsign field, or tabbing out of the Callsign field should update the Capture window items to match those of WinWarbler's QSO Info panel 3.4.1 177 double-clicking a received callsign updates the Capture window items to match those of WinWarbler's QSO Info panel 3.4.2 178 striking Enter in the Callsign field, double-clicking the Callsign field, tabbing out of the Callsign field, or double-clicking a received callsign updates the QSO Info's Freq textbox to reflect the transceiver's current frequency, if Commander is running 3.4.2 179 in CW word mode, don't append a space to the end of the final word 3.4.2 180 use pane 1 for CW so characters received by the external modem (if used) are displayed (reverses bad idea introduced in 3.4.0) 3.4.2 181 adjustments to receive pane splitter bars not working properly (regression introduced in 3.4.0) 3.4.3 182 striking Enter in the QSO Info panel's Callsign textbox doesn't perform a lookup (regression introduced in 3.4.1) 3.4.3 184 the Optimal Offset function fails after a channel's frequency was set by a <rcvchannel> macro 3.4.5 183 ensure exact persistence in display heights when switching modes (don't allow "display xmit/rcv characters" setting to change unless in CW mode) 3.4.6 184 don't perform a DXView lookup when logging a QSO 3.4.6 185 eliminate errorlog.txt entry from WinWarblerMain.Form_Resize 3.4.7 186 don't permit the Main window to be vertically expanded or maximized if in phone mode, or CW mode with "display xmit/rcv characters" unchecked 3.4.7 187 if PSK broadband decoding or channel markers are enabled, the frequency scale is incorrectly positioned above the waterfall during soundcard RTTY operation 3.4.8 188 selecting a different soundcard for PSK operation via the Config window's Soundcard PSK tab should have no impact on Soundcard RTTY operation 3.4.8 189 if WinWarbler was running Soundcard RTTY with the transceiver in LSB or USB during the previous session, then if WinWarbler is started with the transceiver in LSB or USB, SoundCard RTTY operation should be initiated 3.4.9 190 use WaveIn device names rather than Mixer device names to label the soundcard buttons 3.4.9 191 if Contest Mode is not enabled, clearing the QSO Info panel should clear the TX# text box 3.4.9 192 switching to Phone with WinWarbler configured to run SSB doesn't properly select the sideband as a function of frequency 3.5.0 193 if Commander isn't running, WInWarbler doesn't overide soundcard RTTY profile settings with saved settings for AFC, Reverse, Squelch, etc. 3.5.1 194 double-clicking on a Spot Database entry with "Initialize RST fields to 59/599" and "set QSO start when RST Rcvd" set should change the QSO's status to "started" 3.5.1 195 "Initialize RST fields to 59/599" should not overide an RST field that has already been set 3.5.1 196 when directing DXKeeper to create a new entry, include a parameter that prevents DXKeeper from performing overwrite checking 3.5.1 197 settings on the Config window's Soundcard RTTY tab aren't initialized until Soundcard RTTY is running 3.5.2 198 PSK transmit frequency is improperly initialized 3.5.2 199 QSO Info panel's State and County items should appear when the DXCC selector is set to KH6 or KL7 3.5.2 200 navigating to hidden QSO Info items (e.g. Province for a non-Canadian QSO) generates errorlog.txt entries 3.5.2 201 properly convey change in Main window state to the Launcher 3.5.3 202 improperly updating the DXKeeper Capture window with QSO Info panel contents after a DXKeeper lookup for a QSO not directed to WinWarbler 3.5.4 203 on receiving a spot from SpotCollector, don't direct DXKeeper to perform a previous QSO and callbook lookup unless the Automatic Lookup option is enabled 3.5.4 204 WinWarbler incorrectly concludes that DXKeeper is running after DXKeeper has been terminated 3.5.5 205 CTRL-double-clicking a received word while in RTTY mode places the letters-figures-shifted word in the QSO Info panel's Via textbox (regression introduced in 3.5.5) 3.5.7 206 automatic registration of Timer.dll fails if the destination pathname includes folder names containing spaces 3.5.7 207 a callbook lookup (via DXKeeper) should not clear the contents of the QSO Info panel's address, county, state, province, DXCC Prefix, CQ, ITU, or Iota items. 3.5.7 208 when clicking on a monitor channel triangle should initialize the QSO Info panel's transmitter power text box to the specified default transmitter power 3.5.7 209 stacking messages to WinKey garbles a character in the currently-transmitting message 3.5.9 210 enable DTR and disable RTS to properly power a standalone WinKey 3.6.1 211 eliminate multichannel scanning when not enabled 3.6.2 212 if multiple messages are queued when operating CW in WinKey, a single ESC aborts them 3.6.2 213 eliminate delays between characters when transmitting in CW using WinKey 3.6.2 214 correctly implement the <CWSpeed: N> macro for use with WinKey 3.6.2 215 don't inform PSKCORE about changes to monitor channel AFC or squelch levels unless broadband decoding is enabled 3.6.3 216 eliminated overflow in CWXCVR.RecomputeWPM 3.6.3 217 improve WinKey buffering scheme 3.6.4 218 if path to REGSVR32.DLL can't be found, prompt user to specify it 3.6.4 219 properly resize the minimized Main window when the mode is changed by a spot database double-click 3.6.4 220 aborting a WinKey transmission is unreliable 3.6.5 221 when generating CW via WinKey and the serial port is changed, re-initialize the WinKey 3.6.5 222 DXKeeper's Capture window frequency is not initialized when WinWarbler starts in CW, Phone, or RTTY via external modem 3.6.6 223 when converting PTT lead and lag times to 10ms steps for WinKey, round rather than truncate 3.6.7 224 eliminated an errorlog.txt entry introduced by a regression in 3.6.6 (type mismatch in WinWarblerMain.RTTYReceiveFreq_Change 3.6.7 225 min WPM and max WPM labels were reversed in the WinKey speed potentiometer panel 3.6.7 226 directly compute phone window height rather than rely on saved value 3.6.8 227 expanding the QSO Info panel excessively increases the window height 3.6.8 228 correct regression in TimerMM.DLL installation; provide a robust component-registration mechanism that does not require user intervention 3.7.0 229 eliminate errorlog.txt entry if WinWarbler starts up with Commander indicating a transceiver frequency of 0 3.7.2 230 With the QSO Info panel expanded in Phone mode, contracting the QSO Info panel doesn't reduce the size of the Main window 3.7.3 231 the allocation of space among the PSK or RTTY display panes is not accurately maintained between mode changes or QSO Info panel expansion/contraction 3.7.3 232 return cursor focus to Main window after clicking the Main window's CW PTT checkbox 3.7.4 233 starting up with CW PTT enabled from the previous session generates an errorlog.txt entry (regression introduced in 3.7.4) 3.7.5 234 contracting a display pane to its minimum height does not cause it to dissappear (regression introduced in 3.7.3) 3.7.5 235 when operating RTTY, don't allow the upper splitter bar to undock unless both soundcard RTTY and external modem RTTY are enabled 3.7.5 236 use HTTP format filenames when invoking the browser on a help file 3.7.5 237 waterfall traces appear for collapsed (disabled) receive panes 3.7.6 238 when generating CW via a WinKey striking ( should send a KN, not an OS 3.7.8 239 initiating a CW transmission via WinKey can be perceptibly delayed 3.7.9 240 provide missing tooltips in Config window controls 3.8.0 241 enable channel markers when switching from MMTTY to PSK operation 3.8.0 242 correct misalignment between waterfall and frequency scale 3.8.1 243 correct lack of precision in RTTY receive frequency display 3.8.1 244 switching to Phone mode with the QSO Info panel's Freq selector empty causes an Errorlog.txt entry 3.8.2 245 clearing the Transmit Pane while operating RTTY should prevent un-transmitted characters from being sent 3.8.3 246 PSK receive and transmit frequencies can be off by 1 Hz 3.8.3 247 clearing the Transmit Pane via the popup menu entry should prevent the transmission of untransmitted characters in RTTY and CW modes 3.8.4 248 outgoing spots do not include the mode in the spot notes 3.8.7 249 outgoing spots do not convey user-specified spot notes 3.8.7 250 report error message to user when attempt to play a sound file fails 3.8.9 251 double-clicking an entry in the Stations Heard window can erroneously initalize the QSO Info panel with the callsign of the station being worked by the heard station rather than that of the heard station 3.9.1 252 correct an overflow in PskXcvr.SelectClickedWord when the receive pane contains more than 65K characters 3.9.3 253 correct a problem in initiating soundcard RTTY when switching to RTTY mode 3.9.4 254 in RTTY operation, disable the OPT button when MMTTY transitions to transmission and reception modes respectively, not when the Start or Stop buttons (or macro commands) are executed 3.9.5 255 disable the Main window's Maximize button 3.9.6 256 macro panel caption is not updated when switching between macro banks using the ALT key 3.9.8 257 eliminate Errorlog.txt entry from MMTTYModule.UpdateSignalStrength 4.0.1 258 if PSK or RTTY band segment definition files are missing, don't generate an errorlog.txt entry unless Log Debugging Info is enabled 4.0.2 259 Double-clicking in a PSK receive pane while depressing the CTRL key should not designate the associated channel as the QSO channel 4.0.2 260 When handling an activated spot, direct DXView to rotate the antenna whether or not "Automatic Lookup" is enabled 4.0.2 261 with PTT via a serial port, startup in soundcard RTTY incorrectly says port is unavailable 4.0.4 262 disable the RTTY transmit panel's reverse box if soundcard RTTY and FSK modulation 4.0.5 263 modifying the Callsign or double-clicking on a callsign in a receive pane clears the DXCC selector, CQ zone, and ITU zone 4.0.5 265 autoarchive disable message doesn't correctly display the rationale 4.0.6 266 don't disable autoarchive on error - just log an message in the errorlog 4.0.6 267 prevent double-open of PTT port via PSKCORE when switching to PSK from RTTY 4.0.7 268 don't set PTT port to 'none' if the specified PTT port fails to open (reverse enhancement #381) 4.0.9 269 disable the macro and transmission start buttons when switching between modes 4.0.9 270 remove trailing blank line from DefaultRTTYBands.txt 4.1.1 271 when directed by SpotCollector to handle a spot for a mode other than PSK, RTTY, CW, or Phone, direct Commander to QSY the transceiver to the spot frequency and set its mode to USB (if the spot frequency is above 10 mHz) or LSB (if the spot frequency is below 10 mHz) 4.1.2 272 the Stations Heard form's data column width does not persist between operating sessions 4.1.3 273 ignore macro invocations while a macro is already running 4.1.3 274 uncheck and disable the Soundcard RTTY panel's Net box when operating FSK 4.1.3 275 disable TX Invert checkbox on Config window's RTTY tab when operating FSK 4.1.4 276 6-character grid squares of the form Ix9xxx specify a longitude that's incorrect by up to 2 degrees 4.1.4 277 repetitively switching between the soundcard RTTY and external RTTY modem panes causes the pane boundary between them to drift 4.1.4 278 repetitively switching between the soundcard RTTY and external RTTY modem panes causes the transceiver frequency to decrease by 10 hz per cycle 4.1.4 279 in PSK and RTTY modes, don't clear the transmit pane when the user clicks the Stop, strikes the F4 button, or invokes a macro containing a <stop> command - wait until transmission is complete to clear the transmit pane 4.1.4 280 when using an ALT shortcut from the Transmit pane, don't leave the ALT box checked unless it was checked to begin with 4.1.5 281 correctly handle remote macro invocations from DXKeeper that invoke DXKeeper functions 4.1.5 282 remember the Heard window's Font Size setting between operating sessions 4.1.6 283 <mycourse>, <mygrid>,<mylatitude>, <mylongitude>, and <myspeed> substitution commands fail unless the Position and Vector window is open 4.1.8 284 ensure that ALT-double-click on a grid square is reliable 4.1.8 285 if an external RTTY modem doesn't support inverted transmission and/or inverted reception, disable the reverse transmit and/or reverse receive checkboxes respectively 4.1.8 286 when operating soundcard RTTY in USB, the transmit and receive frequencies should correspond to the Mark frequency 4.1.8 287 when operating RTTY via external modem in AFSK mode, the transmit and receive frequencies should show the mark frequency for the selected sideband 4.1.8 288 when Shift-F10 is struck to activate a macro with the cursor the QSO info panel's RX# item, the Windows menu appears 4.1.8 289 the <cwspeed: n> macro should take immediate effect 4.1.8 290 pasting information into the transmit pane should not automatically initiate transmission 4.1.8 291 clicking the Abort button in the PSK Transmit or RTTY Transmit panel should clear the Transmit pane 4.1.9 292 if Shift-F10 is struck in any textbox, automatically send another F10 to clear the Windows menu 4.2.0 293 with Contest Mode enabled, do not move the cursor focus after a keyboard shortcut is initiated unless the shortcut is one that explicitly moves the cursor focus 4.2.0 294 prohibit control characters from being entered in the RX# textbox 4.2.0 295 on startup, properly enable or disable contest, RX#, and TX# labels based on the state of Contest Mode 4.2.1 296 re-assign shortcut keys for WPM adjustment in CW mode
- -1 wpm: alt-left arrow (or ctrl-alt-left arrow)
- +1 wpm: alt-right arrow (or ctrl-alt-right arrow)
- -5 wpm: alt-down arrow
- +5 wpm: alt-up arrow
4.2.1 297 re-assign shortcut keys for signal search in PSK31 and PSK63 modes
- next lower frequency signal: alt-left arrow
- next higher frequency signal: alt-right arrow
4.2.1 298 in contest mode, clearing the QSO Info panel should place the cursor in the Callsign textbox 4.2.1 299 with Contest Mode enabled, clicking the Spot, Begin, End, or Help buttons should move cursor focus to the RX# panel; if Contest Mode is not enabled, clicking these buttons should move cursor focus to the Transmit pane 4.2.1 300 double-clicking on a RTTY spot with soundcard RTTY configured for FSK operation sets the transceiver to the wrong frequency (regression introduced in 4.2.3) 4.2.4 301 InvokeSoundcardMacro DDE operation incorrectly reports "failure to execute" 4.2.5 302 don't retry a server that's reported down if a retry is already scheduled 4.2.7 303 when clearing the parallel port, set pin 17 to logical zero 4.3.0 304 ignore requests to close macro window while transmitting 4.3.1 305 ignore requests to edit macros while transmitting 4.3.2 306 "Copy to" window reverses RX# and TX# destinations 4.3.4 307 zero-fill the Stations Heard window's Age data to 3 digits for correct numeric sorting over long acquisition intervals 4.3.5 308 when in RTTY mode and a PSK spot database entry is double-clicked, properly activate the receive pane last active in PSK 4.3.6 309 spots generated while in phone mode contain the last CW frequency instead of the current phone frequency 4.3.8 310 PSK and RTTY sub-band definition file frequencies are not correctly read in non-US locales