Author Archives: Nathan

SpotCollector Defects

Wide variety Description model corrected
1 the caption of length limit panel (on Database Tab of Configuration window) is wrong; the value proven is the cutting-edge variety of entries within the Spot database 1.0.1
2 Spot database window “color coding” on occasion sparkles or disappears 1.zero.1
three Spot database entries need to capture all origins (as opposed to the most recent beginning) and be filtered consequently 1.zero.four
4 Spots don’t appear at the DXView global map, despite accurate filter out settings 1.zero.1
five Disabled DX cluster and/or IRC home windows seem after startup 1.0.1
6 Band, mode, and foundation filters fail to initialize nicely
7 double clicking on a niche in a Telnet DX Cluster window does now not well initialize the DXKeeper capture window 1.0.three
8 no Spot Database entries are created whilst run from locales using dd/mm/yyyy date formats 1.0.6
nine frequencies are displayed improperly whilst run from locales the usage of the comma as a decimal separator 1.zero.6
10 clicking First or ultimate Spot Database navigation button with an empty Spot Database produces a runtime error 1.zero.7
11 clicking on a niche Database entry fails to QSY the transceiver when run from locales using the duration as a hundreds separator 1.0.8
12 clearing the spot database resets the spot clear out and type order 1.1.1
13 choosing a one of a kind Telnet cluster to serve as the Spot vacation spot fails to clean the preceding cluster’s Spot radio button 1.1.2
14 delimiters (e.g. +, -, <, > ) are stripped from notes 1.1.five
15 SpotCollector doesn’t regain get admission to to the modern log’s development table after DXKeeper completes a Recompute development operation 1.1.6
sixteen Spots generated by using a SH/DX are captured with out the QSO mode 1.1.nine
17 Runtime mistakes while run on eastern home windows 1.2.zero
18 unsuitable managing of frequency in non-English locales effects in fallacious band and mode assignments 1.2.2
19 corrects disorder added in 1.1.nine that may produce “illegal use of null” software mistakes 1.2.6
20 saves internet server parameters between periods 1.2.7
21 spot database window size is not preserved between classes 1.three.zero
22 bandmodes.txt record carries extra linefeeds 1.three.1
23 deactivating most important window generates runtime errors if spot database display is empty 1.three.three
24 the need filter works incorrectly when all containers at the Awards tab of DXKeeper’s Config window are unchecked 1.three.three
25 the spot database prune date fails in non-English locales 1.3.five
26 overflow error in clustermodule.processincoming 1.3.6
27 spot database grid column order is not preserved 1.3.6
28 double-clicking on a niche database entry with a cut up frequency does now not well set the transceiver’s VFO-B when walking from a ecu locale 1.3.8
29 double-clicking on a DX spot in a telnet cluster window does not well QSY the transceiver whilst strolling from a european locale 1.3.8
30 numerous home windows have random tab order 1.three.nine
31 spots from the CQDX IRC channel are not captured in case you hook up with the channel #CQDX instead of CQDX 1.4.zero
32 spots erroneously rejected as “too vintage” because month and day of cutting-edge time are reversed during certain date ranges on positive XP systems 1.4.3
33 macro button captions aren’t displayed whilst a packet, IRC, or cluster window is first enabled 1.4.7
34 connecting to packet clusters through nodes, e.g. ‘db0mdx v db0sm’, results in spots no longer being recorded within the spot database 1.four.7
35 TNC version listbox isn’t always populated unless the PacketCluster spot supply is enabled 1.four.eight
36 do not show PacketCluster window if TNC serial port is in use 1.five.zero
37 disable Spot button if no spot supply is chosen 1.five.zero
38 disable Outgoing Spot selector for disabled spot assets 1.5.0
39 the Reset button on the Config window’s show Fonts tab does not reset Packet Cluster shades to their default values 1.five.2
forty show 0 as Ø option would not work 1.five.2
forty one pre-configuring a connection to the CQDX telnet cluster is irrelevant for packetcluster customers with out an internet connection 1.5.3
forty two run-time mistakes after first of all coming into Callsign on a few structures 1.5.three
forty three PacketCluster font and heritage colorations aren’t remembered between sessions 1.5.3
44 WWV panel caption omits time 1.five.five
45 results from SH/WWV don’t update the WWV panel or PropView if they’re extra latest that the cutting-edge values 1.five.5
46 Packet cluster font and history shades are set to black the primary time SpotCollector is administered after set up 1.five.6
47 QSX frequencies with extra than 10 digits generate an errorlog.txt report 1.5.7
48 illness introduced in 1.5.7 prevents hyphens in cluster login fields from running successfully 1.5.8
forty nine an incoming spot with an unlawful (e.g. non-numeric) frequency causes a kind mismatch record in errorlog.txt 1.5.9
50 outcomes of a SH/WWV command are not captured for 1-digit dates 1.5.nine
fifty one a niche request thru WinWarbler whilst no spot source is selected outcomes in an errorlog entry 1.6.zero
52 the DXCC usa name popup that appears whilst the mouse cursor hovers over a DXCC prefix inside the Spot Database window presentations incorrect county names for sure DXCC prefixes 1.6.0
fifty three routinely generated Prune dates are incorrect 1.6.0
54 terminating SpotCollector through the windows assignment manager, but logging off the modern-day windows person, or with the aid of shutting down home windows loses the Band, clear out, and Mode settings 1.6.1
fifty five person adjustments to the spot database grid show’s column order are retained without distorion 1.6.three
fifty six spot database grid show column selections are not reset with the aid of incoming spots 1.6.3
57 on every occasion the spot database window loses focus, the spot database grid show is set to autoscroll mode 1.6.3
fifty eight webserver does not take care of appended port# (e.g. http:/192.168.1.1/spots:eighty ) 1.6.6
59 cannot close information window 1.6.7
60 Continent filter window tooltips are ambiguous 1.6.8
sixty one Mode clear out button tooltip is incorrect 1.6.8
62 Spot Database grid font metrics are not stored between classes 1.6.8
sixty three Continent facts routine generates errorlog entries whilst the continent is indeterminate 1.6.9
64 on startup, spot data for preceding hour’s spots (if any) are incorrect if filters have been in force while SpotCollector become last shutdown 1.7.zero
65 band, mode, continent, and origin filters do not well initialize on startup (regression delivered in 1.6.6) 1.7.three
66 the consequences of SH/WWV are not well captured whilst running a non-English locale 1.7.three
67 UpdateSpotStatistics loop 1.7.four
68 want filter out displays spots of stations already worked 1.7.four
sixty nine deal with unlawful Config settings with out termination 1.7.four
70 Spot information are invalid inside the origin clear out isn’t always set to All 1.7.6
seventy one Requery log recordset while a brand new log entry is brought 1.7.five
seventy two Compact the Spot Database at startup, and on every occasion it’s miles cleared 1.7.five
seventy three take away useless database actions while updating an present Spot Database entry 1.7.five
74 when conveying a gap to DXView, ship the timestamp from the spot in preference to the current computer’s time 1.7.7
seventy five generating a niche from locales no longer the use of . as the decimal separator will fail 1.7.8
seventy six gracefully cope with spots whose frequency is a unmarried decimal factor 1.eight.0
77 consequences of SH/WWV from a packetcluster uses the font color specific for TelnetCluster WWV consequences as opposed to PacketCluster WWV effects 1.8.0
78 constantly look for the solar records report SolarHistory.txt in SpotCollector’s folder 1.eight.2
79 at once keep Band filter out, Mode filter, beginning filter, and Continent filter modifications, in place of wait till SpotCollector is terminated 1.8.2
80 within the solar history show, the lower bound for the A index axis can be incorrectly computed, ensuing in A values plotted beneath the Date axis 1.eight.2
eighty one main or trailing areas appended to cluster or IRC addresses prevent connection 1.eight.three
eighty two dispose of blunders that may occur whilst the Spot Database is empty 1.eight.7
eighty three do not automatically permit the logging of diagnostic data when an error occurs 1.eight.7
eighty four remove regression in Spot Database show 1.8.8
85 forget about WWV spots whose SFI, A, or k parameters are out in their described tiers 1.nine.1
86 accurate blunders sun history k axis that occurs with very massive A 1.9.1
87 immediately “repaint” Spot Database display after a double-click 1.9.1
88 Spot records not visible 1.9.3
89 accurate regression introduced in 1.nine.1 that prevents the capture of SH/WWV outcomes from Telnet or Packet clusters walking CLX software 1.9.6
ninety error whilst showing Config window 1.nine.7
91 changes to the Audio Alarm sound pathname entered through the keyboard are not saved among sessions 1.nine.7
92 show manage explanations checkbox placing is not stored among classes 1.nine.7
ninety three Gracefully deal with and record an already-open internet server port 1.nine.nine
94 while examining the effects of a SH/DX operation on a telnet cluster or packet cluster, extract the date from the spot in preference to expect “nowadays” 2.zero.0
ninety five after the a left-click on a niche Database entry, wait half a second before acting a DXView research to be sure that the left-click is not the primary-half of of a double-click 2.zero.1
96 text pasted right into a cluster window transmit pane is invisible on a few structures 2.0.1
ninety seven gracefully cope with spots with bogus frequencies 2.0.2
ninety eight KG4XXX calls are from america fourth name area, not Guantanamo 2.zero.four
ninety nine Spot Database tooltips must be suppressed if the Spot Database is empty 2.0.five
a hundred do not require Commander to be running that allows you to perform a niche from DXkeeper’s seize window 2.0.6
one zero one Frequency clear out fails in non-English locales 2.zero.7
102 putting an ESC inside the PacketCluster window appends the escape character to the quit of the transmit window and repositions the cursor to the start of the transmit window instead of inserting the ESC at the selected function 2.0.8
103 Unneeded spot database entries are rendered in black in preference to in the colour unique at the Config window’s display Fonts panel 2.0.8
104 The internet server generates an Errorlog.txt entry if the spot database is empty 2.0.eight
one hundred and five double-clicking on a RTTY spot database entry initializes DXKeeper to the RTTY transceiver mode (which might be set to USB) rather than RTTY 2.1.0
106 spelling error in DXCC tooltip 2.1.zero
108 usually set windowstate to everyday earlier than saving window function; then restore windowstate 2.1.zero
109 KL7 beginning must be NAW, no longer SA 2.1.1
107 PSK spot database entries have to be flagged as “wished” for RTTY 2.1.2
one hundred ten dispose of “reasonability” regulations on the price at which the A index can trade 2.1.2
111 for spots through NA stations no longer in ok, VE, or KL7, use CQ zones to decide whether or not they are in NA-E, NA-M, or NA-W 2.1.3
112 DXCC prefix no longer supplied to DXKeeper whilst in log filter is “entity” (regression brought in 2.1.eight) 2.1.9
113 “up 1” QSX is improperly computed (regression brought in 2.2.1) 2.2.2
114 store adjustments to Cluster, IRC, and Packet window font setting without delay, as opposed to waiting for SpotCollector shutdown 2.2.3
a hundred and fifteen DX clusters incorrectly car-reconnect in sure circumstances 2.2.4
116 initialize Cluster and IRC font settings on startup rather than anticipating Cluster window or IRC window initialization 2.2.4
117 while first established, wait to display the main window till the consumer has specified a callsign 2.2.four
118 successfully handles ‘Simplex’ in Spot notes of a brand new spot database access 2.2.4
119 shop Cluster and IRC setup parameters while they’re changed, rather than at program termination 2.2.5
one hundred twenty FM mode spots are introduced as “Martinique” 2.2.6
121 KG4 2×1 callsigns are within the US, not Guantanamo 2.2.7
122 ZC4 spots are announced as Cyprus as opposed to “Cyprus uk military Bases” 2.2.7
123 correct frequency alignment in Spot Database record 2.2.9
124 in no way transmit slashed zero characters to telnet clusters, IRC clusters, or packet clusters 2.2.9
one hundred twenty five save Packet setup parameters while they are modified, instead of at application termination 2.2.9
126 /CTCP dxs sh/wwv 30 inside the IRC window fails if carried out throughout January 2.three.four
127 Spot document generates errorlog.txt entries 2.3.5
128 a spot database entry created by a gap whose starting place is hidden by the origin filter will no longer be introduced while a later spot is received from a non-hidden starting place 2.three.6
129 the ZC4 assertion contains extraneous data 2.three.6
130 SpotDatabaseUI.FetchRowStyle generates an errorlog.txt entry whilst encountering null database fields 2.three.7
131 apprehend “SSB” as a criminal mode while analyzing spot notes 2.3.8
132 “up X” where X is bigger than 32767 generates an errorlog.txt entry 2.3.nine
133 double-clicking on a gap Database access disables autoscroll, however the “pass-to-last” arrow isn’t enabled until the next spot arrives 2.4.0
134 the filter panel caption is erroneously initialized to “None” 2.four.zero
one hundred thirty five the Mode and Continent filter home windows must now not be resizable 2.4.0
136 ensure that the Spot Database Grid is selected while the consumer clicks the record selection column in order that striking the Delete key deletes the entry 2.four.1
137 double-clicking on a gap Database entry does not replace Pathfinder with the callsign if DXKeeper is running and there are previous QSOs with the noticed station 2.four.2
138 spot notes conveyed in spots from other DXLab applications need to seem in the spot notes textbox, now not appended to the callsign textbox 2.four.3
139 terminate through unloading all contributors of the paperwork series rather than invoking stop 2.4.five
140 set QSX to zero before directing WinWarbler to QSY if “Set Xcvr break up” is disabled 2.four.6
141 SpotCollector fails to shut effectively on a few systems (regression delivered in 2.four.6) 2.4.7
142 when shutting down, send every related Telnet cluster a “Bye” command before terminating the relationship 2.4.nine
143 the web server have to reply to a WebDAV techniques with a “501 now not carried out” response 2.five.zero
one hundred forty four whilst disconnecting from a cluster, most effective ship a “Bye” command if the telnet connection continues to be connected 2.5.2
145 checking wrong DXKeeper registry access for PSK award enablement 2.five.four
146 prevent incoming spots from reversing the relocation of a gap database column 2.5.6
147 SpotDatabaseModule.SpotGridScrolled generates an errorlog.txt access 2.5.8
148 if Autoscroll is disabled or a column move is in progress, show a blue “Autoscroll Disabled” indicator and preserve the Spot Database display stable by means of not displaying new Spot Database entries; if new spot database entries arrive while Autoscroll is disabled, alternate the colour of “Autoscroll Disabled” from blue to pink. 2.five.nine
149 put off errorlog.txt entry from UpdateKeyboardHeight in ClusterDisplayModule, IRCDisplayModule, and PacketDisplayModule 2.6.1
a hundred and fifty FormatLogDisplay can replace the cutting-edge column widths with default widths 2.6.three
151 Autoscroll is autonomously re-enabled via the subsequent new Spot Database entry after the Spot Database display’s Column widths are adjusted or after the currently-decided on Spot Database entry is clicked 2.6.three
152 Use 10mHz to pick among USB and LSB 2.6.4
153 the DXCC entity for a callsign bearing a /N where N is a unmarried numeric digit need to be decided through substituting N for the right-most digit in the prefix (as opposed to the left-maximum digit) 2.6.5
154 characters pasted into a cluster, IRC, or packetcluster window’s Keyboard pane the usage of a CTRL-V do no longer seem, though they are present 2.6.5
a hundred and fifty five nicely decode the DXCC entity of callsigns like KG4XXX/B, KC4AAA/QRP, and KC4/AA6YQ whilst DXView is not going for walks 2.6.6
156 ship accelerated spot data in DDE command to WinWarbler in order that it could generate outgoing DDE commands to DXKeeper and Pathfinder (rather than permit SpotCollector try this, which induced a race circumstance) 2.6.7
157 work round lacking “Z” in instances obtained from #CQDX that have been generating spurious QSX frequencies 2.6.7
158 if attempting to examine development from the currently-open log’s development desk fails, try to get better by using remaining and then-reopening that log 2.6.7
159 the forward navigation button works efficaciously 2.6.8
a hundred and sixty make sure that retrying useless servers would not intrude with in-development cluster connections 2.7.zero
161 while the Band filter is ready to “transceiver band only”, a new frequency have to most effective replace the band filters if the band has changed 2.7.1
162 eliminates immoderate CPU consumption while resizing the primary window 2.7.four
163 if the response to a SH/DX contains no spots notes however its predecessor precise a QSX, the Spot Database access could be erroneously created with the predecessor’s QSX 2.7.five
164 suppress any QSX whose band doesn’t fit that of the DX station’s transmitting frequency 2.7.5
166 use HTTP layout filenames when invoking the browser on a assist record 2.7.6
167 don’t despatched spots to Commander that do not live on the current Band filter out 2.7.7
168 do now not replace Spot Database progress when DXKeeper logs a QSO to a log apart from the only SpotCollector is referencing for award progress 2.7.eight
165 sure actions cause the Spot Database to temporarily lose its font colorations 2.7.9
166 from a prefix-mapping angle, deal with callsign/N wherein N is an integer super than nine as callsign 2.8.zero
167 remove mapping of KC4XXX to Antarctica; let the DXCC database discover individual Antarctic calls 2.eight.1
168 deletion affirmation causes utility crash (regression introduced in 2.8.2) 2.eight.3
169 for callsigns of the form A/B, if the length of A is same to the duration of B, then A designates the DXCC entity 2.eight.4
170 clicking on a column to the left of the Callsign column disables autoscroll 2.8.four
171 putting characters in the IRC window’s transmit pane before a connection is made causes a runtime errors 2.eight.5
172 don’t show tooltips when the mouse cursor hovers over unused quantities of the spot database display 2.eight.5
173 correct disorder that could result in replica spot database entries in reaction to sh/dx 2.8.5
174 “play intro on startup” appears on all Config window tabs 2.eight.7
one hundred seventy five correct regression introduced in 2.8.5 that reasons inconsistent updates of current spots in pruned spot databases 2.9.1
176 ensure the spot database is nicely rendered after a trade in filter 2.nine.3
177 when figuring out whether a callsign has been formerly labored in PSK, consist of PSK63 QSOs 2.9.four
178 operating a formerly-wanted PSK station does not well update the spot database entry coloration 2.9.4
179 on startup, make certain that left-most column is visible 2.9.5
180 reject unlawful net server request as “unsupported” 2.9.6
181 forget about callsigns containing an apostrophe 2.nine.9
182 reduce spotgrid celltips postpone to triumph over intermittency 2.nine.nine
183 request a frequency replace from Commander before producing a niche 3.zero.0
184 restrict immoderate font sizes within the Spot Database display three.0.0
185 accurate miscoloring of RTTY and PSK Spot Database entries three.0.0
186 with DXView not walking, nicely decode callsigns of the form RA3XX/6/P three.0.1
187 permit login to the $CQDX IRC cluster with a callsign beginning with more than a few 3.0.2
188 disable the popup menu’s Request Propagation Forecast object if DXView isn’t always jogging 3.zero.three
189 mark automated DXView replace requests as ignorable three.zero.4
190 efficiently manage the case in which DXView clears the LotWDatabase filename 3.0.5
191 put off errorlog.txt entry generated with the aid of HiddenFilterUI.UnHideCmd_Click while the Spot Database show is empty three.0.7
192 eliminate errorlog.txt entry generated by way of SpotDatabaseUI.SpotGrid_Click when right-clicking a header row three.zero.7
193 ship the right mode specification to Commander and WinWarbler when CW-R is chosen three.1.2
194 if the mode is not exact in the spot notes, decide it from DX station’s transmit frequency, now not the QSX frequency 3.1.3
195 a “force rejection” error going on when attempting to connect to a telnet cluster need to not generate an errorlog.txt entry 3.1.6
196 if a gap’s callsign is overridden, it must no longer be considered a fit with present spot database entries created before the override become designated 3.1.8
197 if the required spot database filename does not exist and can’t be created, tell the person but don’t generate an errorlog.txt entry and do not permit the DAO datasource selection windows to appear 3.1.9
198 extract QSX frequencies from neighborhood spot notes submitted via WinWarbler 3.1.nine
199 use operator region in spot database entries generated or up to date through the person’s spots 3.2.zero
200 properly combine spots for which an entity override is active into a single spot database access 3.2.6
201 CTRL-clicking an sq. filter out button need to make certain that the square filter window isn’t minimized 3.2.7
201 well deduce the DXCC entity of callsigns like VU4AN/VU3ABC 3.2.8
202 catch up on CQ-DX failure to insert a area between callsign and spot notes if callsign is greater than 12 characters in length 3.2.9
203 efficiently put in force the initial cluster command for PacketClusters three.three.3
204 when a spot database access is clicked or double-clicked, make sure that the desired callsign is despatched to DXView 3.3.5
205 ensure that clicking the remaining spot database access sends the required callsign to DXView 3.3.6
206 don’t send preliminary cluster command when acting a cluster keep-alive operation three.three.7
207 make certain that “clean spot database on startup” works reliably three.three.nine
208 accurate band and mode clear out initialization regression introduced in three.3.nine 3.four.0
209 properly spot to IRC from external programs three.4.1
210 ‘”unhide” IRC window whilst its LED manage is clicked three.4.4
211 if the spot database can not be compacted on startup, tell the person instead of generate an errorlog.txt access 3.4.6
212 cast off an errorlog.txt entry that can be generated by DDEServerModule.Enqueue three.4.7
213 efficiently compute CountryProgress 3.five.1
215 prevent an errorlog.txt access from being created when saving an empty unique name list three.5.three
216 prevent an errorlog.txt entry from being created whilst clearing or sorting an empty special name listing three.five.four
217 whilst developing an entity override by way of right-clicking on a spot records entry, pressure the Config window to expose its Entity Overrides tab three.5.four
218 on net pages generated by using the web server, set the font color of established Spot Database Entries to inexperienced, no longer pink 3.five.four
220 leading or trailing areas on an entity override callsign should not prevent a healthy with a spotted callsign 3.5.four
219 on net pages generated by means of the web server, specify using a non-proportional font to ensure column alignment three.5.five
214 guarantees that the selection of a gap Database access isn’t altered via incoming spots three.5.6
215 keep spot notes whilst the transceiver’s frequency or split modifications 3.five.eight
216 save you spurious DXView lookups three.five.9
217 efficaciously update spot notes when the transceiver’s frequency or break up modifications three.6.0
218 do not disable spot dequeueing if the user clicks on a gap Database column heading 3.6.2
219 re-permit spot dequeueing after a column circulate operation 3.6.three
220 if the Spot Database pathname is invalid, show a message in place of generating an errorlog.txt document 3.6.5
221 successfully update Spot Database display font hues after invoking the following Spot or preceding Spot capabilities three.6.7
222 accurate a defect that effects in a confirmed Spot Database access being coloured as showed after a QSO is logged 3.6.7
223 receipt of an outgoing spot via DDE ought to allow autoscroll if it changed into disabled three.6.nine
224 correct DDE cluster spot regression in three.6.nine 3.7.0
225 DDE instructions to generate outgoing cluster or nearby spots need to no longer purpose SpotCollector to thieve recognition 3.7.2
226 click the AutoScroll Disabled indicator must reliable permit AutoScrolling whilst the indicator is blinking 3.7.2
227 don’t generate an errorlog.txt access while the user changes the spot database access row peak three.7.4
228 if the user changes the spot database access row top, consider it between operating periods three.7.4
229 enhance wording in Award development window 3.7.7
230 while conveying a propagation forecast directive to PropView, encompass the frequency 3.7.nine
231 do not enforce window width and height regulations if “use dual video display units” is enabled 3.eight.1
232 set cluster fame display to crimson at some stage in all telnet errors 3.8.2
233 while developing an entity override via the right-mouse menu, deliver the information to DXView three.8.four
234 prevent an errorlog.txt entry when clicking a cluster window’s Disconnect button (regression added into three.8.3) three.8.four
235 do not generate an errorlog.txt access if the person proper-clicks underneath the final spot database entry 3.eight.5
236 efficiently validate a cluster connection while the specified consumer name does not exactly suit the specified operator callsign three.8.five
237 make sure that the cumulative spot notes window completely presentations its vertical and horizontal scroll bars while needed three.eight.7
238 properly deliver spots of tagged unique callsigns to Commander 3.eight.eight
239 while activating a 60m SSB spot, direct Commander to set the transceiver mode to USB three.9.2
240 a split frequency located inside the outgoing spot notes have to not encompass a heaps separator, because it prevents the resulting spot notes from being properly parsed on arrival 3.9.3
241 when creating a gap database access whose callsign has an entity override, decide the continent from the entity override, now not the callsign 3.nine.4
242 while the internet server gets an incorrect command, ship back an explanatory error message 3.9.6
243 when pronouncing a callsign, well handle a forward scale down or a backslash 3.9.7
244 well announce a callsign containing a Ø three.9.7
245 reduce the possibility that a brand new spot will be brought to the Spot Database display simply as the user is clicking or double-clicking three.nine.nine
246 make sure that a DXView lookup initiated by using clicking on a niche Database entry is not altered through a simultaneously incoming Spot Database entry four.0.2
247 take away redundant prefix research (added in four.0.2) four.0.3
248 use synchronous research when an automated Propview forecast is to be generated four.0.five
249 well announce unique callsigns 4.0.7
250 include the most distance to spotting station in newly-created spot database entries four.0.nine
251 correct spot station places for Canadian callsigns
VE9 => NA-E
VE0 => unknown (maritime mobile)
VY0 => NA-M (Nunavut)
VY1 => NA-W (Yukon)
4.1.1
252 accurate spot station locations for Canadian callsigns
VY0 => NA-E (Nunavut)
4.1.2
253 change OMX and OMDX column headings to OMX and OMDX 4.1.2
254 correct spotting station places for Canadian callsigns
VY2 => NA-E (Prince Edward Island)
VE6 => NA-W
VE8 => NA-W
4.1.three
255 ignore WWV spots whose solar flux index is less than sixty four four.1.four
256 with the Band filter’s “enable begin/cease & Max starting place DX Filtering” enabled, the spot database display scrolls to display new spots although autoscroll is disabled four.1.6
257 while reporting award repute for bands now not tracked with the aid of DXKeeper, file band fame as “not tracked” four.1.7
258 replace inactive default spot sources, effectively label KS4Q 4.1.7
259 dispose of errorlog.txt entry brought on whilst generating an outgoing spot through PacketCluster four.1.8
260 accurate type mismatch in CallGridDatabaseModule.USCallArea four.2.zero
261 KC4 callsigns now not located in the USAP database have to now not map to Antarctica 4.2.1
262 KG4 callsigns not of length five ought to no longer map to Guantanamo 4.2.1
263 Callsigns like N6TR/7 have to go back a time-honored 7-region region instead of perform a USAP research on N7TR four.2.1
264 USAP database lookups of stations in Washington DC need to go back a state of Maryland 4.2.1
265 successfully update SpotterGrid and distance to SpotterGrid in current Spot Database Entries 4.2.3
266 eliminate errorlog.txt access generated from SpotDatabaseModule.Dequeue claiming that SpotGrid is null four.2.5
267 get rid of errorlog.txt entry generated by using NotesForm.Form_Resize four.2.6
268 put off errorlog.txt access generated with the aid of ClusterUI.Form_Resize, IRCUI.Form_Resize, and PacketUI.Form_Resize 4.2.6
269 cope with case wherein look for preceding spots without delay after spot database prune does no longer come across BOF four.2.9
270 make sure that unmarried-clicking the last spot database entry immediately conveys the entry’s callsign to DXView four.3.0
271 successfully compute CountryWorked development while DXKeeper reports a change in progress four.3.three
272 don’t set a spot Database entry’s “Band labored” or “usa labored” fields to ‘Y’ until “Band development” is ‘W’ 4.3.4
273 do not set a niche Database entry’s “Mode labored” or “us of a worked” fields to ‘Y’ unless “Mode development” is ‘W’ four.three.4
274 prevent PSK QSOs from incorrectly being coloured as “wanted” 4.three.4
275 make certain that sunrise and sunset instances supplied by DXView in the Band filter out window are displayed with four-digit UTC instances four.three.four
276 do not interpret the effects of a SH/WCY command as WWV information four.three.five
277 revert to continually updating BandWorked and ModeWorked objects four.3.7
278 restore #272 and #273 four.three.eight
279 regulate log database question that produced erroneous “worked earlier than” results on a few systems 4.3.nine
280 regression in 4.3.9 if a spot’s mode is special within the spot notes, don’t override it with the mode decided by way of the spot’s QSX frequency four.4.zero
281 while an entity override is created thru DXView, ensure that it’s far straight away applied four.four.1
282 do not show tooltips inside the Spot Database display if the “show control motives” option is disabled 4.four.3
283 without delay disable processing of queued spot database entries when MouseDown occasion takes place 4.four.3
284 seize all pick out spot records concurrently to save you skew 4.four.4
285 accurate disorder in four.four.4 that precipitated double-clicking a spot database entry to be disregarded in a few instances four.4.5
286 correct defect in four.four.five that untimely re-allows incoming spot processing whilst a double-click on stays viable 4.four.6
287 when processing a niche Database entry double-click on, disable the pending research generated via the primary click 4.four.7
288 replace the Spot Database show after including a brand new access in a manner that doesn’t reason the display to flicker 4.4.eight
289 remove errorlog.txt access generated by using PacketUI.ConnectCmd_Click while no packet callsign is detailed four.5.zero
290 boom performance of FormatLogGrid via doing away with references to the home windows Registry 4.five.zero
291 do not generate an errorlog.txt entry if the net server cannot concentrate because the address is in use four.five.1
292 cast off overflow errorlog.txt entry in WebServer_DataArrival four.five.1
293 cast off overflow errorlog.txt access in ClusterUI.DoConnect four.5.1
294 growth timeout on Commander DDE objects to 30 seconds; if a timeout happens while generating a gap, file this to the consumer instead of producing an errorlog.txt entry 4.five.1
295 eliminate spot database references in SpotDatabaseUI.SpotGrid_FetchRowStyle four.5.1
296 tolerate invalid show settings recovered from the registry on startup pre-initializing to defaults four.5.three
297 prevent an errorlog.txt access from being generated whilst double-clicking the Spot Database show’s caption row four.5.four
298 accurate regression in Spot Database display column order persistence four.five.6
299 tolerate bogus enter to not unusual.IsInteger 4.5.7
300 while dx and/or spotter gridsquares in spot notes are ambiguous, forget about them in place of guess 4.five.7
301 within the special Callsign listing, deal with tags comprised most effective of spaces as though they were empty 4.5.nine
302 efficaciously cope with unique Callsign checking for noticed callsigns containing a / 4.5.9
303 save you the join button caption on the Config window’s general tab from becoming unreadable after the button is clicked 4.6.2
304 whilst invalid settings are discovered in the registry, update the registry with default values and create errorlog.txt entries if “log debugging data” is enabled 4.6.five
305 save you errorlog.txt access generated by way of SpotDatabaseModule.InsertCumNotes when spotting callsign is longer than 13 characters four.6.eight
306 prevent errorlog.txt access whilst spot source caption is greater than 13 characters 4.6.8
307 disable the Maximize button in all spot supply windows four.6.8
308 maintain the the Spot Database display’s horizontal scroll positions four.6.nine
309 don’t generate an errorlog.txt entry when encountering a prefix now not contained inside the DXCC database 4.7.0
310 well interpret SS and SR in the Band clear out window four.7.0
311 prevent errorlog.txt entry in XCCDatabaseModule.GetLocationContinent four.7.2
312 consult the USAP database when examining KH1, KH3, KH4, KH5, KH7, and KH9 callsigns 4.7.three
313 cast off the want to terminate DXKeeper and Commander earlier than the Launcher can improve SpotCollector four.7.3
314 if a band filter out begin or cease time is invalid, change its font colour to red rather than clear it 4.7.4
315 hold the current Spot Database filter whilst compacting the Spot Database four.7.five
316 when the “Date & Time sort Order” panel is ready to “Descending”, properly put into effect the VCR-like controls governing the location of the selected Spot Database access four.7.eight
317 clicking the filter panel X button while miserable the CTRL key ought to disable the LotW and eQSL filters four.7.9
318 clicking the “Autoscroll Disabled” warning have to effectively reposition the Spot Database show while taken care of in descending order 4.eight.zero
319 gambling the incoming speak/personal message alert should no longer require audio announcements to be enabled 4.8.1
320 don’t bear in mind responses to /CTCP commands to be private messages 4.eight.2
321 remove the need to surround square substitution commands like with parenthesis four.8.3
322 for PSK31 spots “detected” by way of frequency in place of spot be aware, trade mode to PSK four.8.four
323 improve interpreting of callsigns of the form part1/part2 where part2 is a single letter four.8.5
324 make sure that all PSK31 spots are recorded with a mode of PSK 4.eight.5
325 nicely put into effect Olivia mode filtering 4.eight.eight
326 store SpotGrid peak in home windows Registry after the “Set Row peak” characteristic is invoked 4.8.eight
327 correct faulty sq. expression for need when want clear out is about to Unworked 4.9.1
328 efficaciously extract the spot time from the result of a SH/DX packetcluster command whilst running in a non-English locale four.9.2
329 accurate regression in coloring of special callsigns four.9.3
330 while a DX gridsquare is received from spot notes, recompute the azimuth based on this grid rectangular 4.9.five
331 while expanding a substitution command, append a “line feed” to every line earlier than sending it to the cluster 4.9.five
332 if the net server is enabled, restart it after pruning or clearing the spot database four.nine.6
333 if the person selects the “create entity override” proper-mouse menu entry however all entity overrides are in use, shows a message informing the consumer 4.9.7
334 if the internet server’s attempt to ship an HTML web page is rejected, restart the web server 4.9.7
335 ensure that LotW and eQSL membership are efficiently conveyed to Commander’s bandspread 5.zero.zero
336 do not convert asc 216 (slashed zero) characters in outgoing cluster messages to asc 48 (zero) whilst running with a code page that doesn’t outline asc 216 as “slashed 0” (e.g. central Europe, Cyrillic, Greek, Hebrew, Arabic, Baltic, Thai, jap, Simplified chinese, Korean, traditional chinese language) five.zero.2
337 on startup, do not recreate an override that become deleted through DXView at the same time as SpotCollector wasn’t jogging 5.0.four
338 while developing an override, clean all of the override’s additives after placing the callsign 5.zero.4
339 while a QSO is logged, properly update the wanted discipline of every affected Spot Database entry five.0.4
340 when developing an override, direct DXView to clean the override’s expiration date component after putting the callsign five.zero.6
341 correct tab order on Config window’s Override tab 5.zero.7
342 populate an override when striking the input key with recognition in the override’s entity selector, no longer whilst striking a letter key 5.zero.7
343 trim facts from overrides to match in spot database fields five.0.eight
344 prevent an errorlog.txt access from being generated through SpotDatabaseModule.InsertCumNotes five.0.9
345 save you errorlog.txt entry generated in SpotDatabaseUI.SpotLastCmd_Click five.1.0
346 reduce CPU and memory aid intake 5.1.1
347 cast off unnecessary Log recordset requery five.1.2
348 make certain that the Spot Database display’s vertical scrollbar is absolutely seen on Vista and windows 7 structures five.1.2
349 reduce resource consumption when web server is disabled 5.1.2
350 make depressing the CTRL key whilst clicking the prev or next spot buttons behave nicely whilst the Spot Database show type order is ascending 5.1.three
351 correct illness in CTRL-Prev-Spot and CTRL-next-Spot 5.1.4
351 save you the Spot Database show’s row peak or font size from exceeding reasonable values 5.1.5
352 save you errorlog.txt file access whilst clearing the Spot Database because of regression introduced in five.1.five five.1.6
353 save you errorlog.txt access generated by means of WebServerModule.DisplayField 5.1.7
354 at the same time as loading or saving a special callsign record, trade the mouse cursor to an hourglass 5.2.0
355 accurate regression in spot database creation 5.2.zero
356 don’t generate an errorlog.txt entry when updating an empty unique Callsign database 5.2.2
357 accurate regression in Spot record that reasons incorrect facts to be displayed five.2.three
358 correct regression that causes hide/Unhide to no longer paintings 5.2.4
359 boost up LocaleInfo.GetLocaleANSICodePage five.2.5
360 make certain that the vertical scrollbar in spot supply home windows is completely seen on Vista and home windows 7 structures five.2.6
361 depressing the CTRL key at the same time as clicking the filter panel X button need to display all Spot Database display entries with out clearing the Band, Mode, beginning, and Continent filters and changing each Spot Database access’s Hidden area to ‘N’ five.2.7
362 do not announce CQ zones if realtime award tracking for WAZ is disabled in DXKeeper 5.2.7
363 tolerate registry mistakes whilst restoring preceding consultation values for process priority and operator vicinity five.2.eight
364 get better gracefully if DXKeeper’s exact mode definition record does now not exist 5.2.9
365 accurate a regression in five.2.9 that prevents spot activation while DXView isn’t strolling 5.three.zero
366 gracefully get better while restoring a corrupted integer price from the windows Registry 5.three.2
367 prevent errorlog.txt entry technology in SpotDatabaseModule.UpdateProgress, kingdom = 24 five.3.four
368 prevent errorlog.txt access generation in SpotDatabaseModule.DoProgressRecomputation, nation = 7 five.three.four
369 replace < and > with escaped characters in net server output five.3.5
370 when developing a gap Database access, nicely initialize the fields representing the regions from which the access changed into now not noticed five.three.6
371 if the Spot Database display turned into sorted by means of double-clicking a column header, then ultimately clicking one of the 6 sort panel buttons ought to reset the type panel caption 5.3.7
372 when updating an current Spot Database access with a spot that has no spot notes, recover the DXGrid and SpotterGrid from the prevailing access earlier than directing DXView to devise the spot five.3.7
373 manage country codes in the variety of 900..999 5.three.9
374 consist of the DXCC entity while checking to peer if a callsign has been labored earlier than five.three.nine
375 while loading a unique callsign list, locate an access whose callsign or tags are too lengthy, tell the consumer, and forget about the access five.4.2
376 disable the processing of incoming spots at the same time as appearing a prune operation 5.4.2
377 prevent an errorlog.txt access from being generated with the aid of ClusterUI.HandleIncomingData five.four.3
378 save you an errorlog.txt entry from being generated via SpotDatabaseModule.RecordSpot 5.4.three
379 tolerate the appearance of greater than 32K characters in a telnet packet five.four.four
380 with the Freq filter out enabled, do not direct Commander to clear its Bandspread window while the transceiver QSYs with out changing bands 5.four.4
381 update defunct default spot sources with lively ones 5.4.6
382 eliminate loop in SpotDatabaseModule.AddOrigins five.four.6
383 suspend input processing when dequeueing is asked 5.4.7
384 handiest suspend enter processing when immediately dequeueing is asked five.4.nine
385 prevent errorlog.txt access in DXSolarModule.LoadSolarHistory 5.five.1
386 save you errorlog.txt access in SpotDatabaseModule.RecordSpot from null mode five.5.2
387 save you errorlog.txt access in SpotDatabaseModule.InsertCumNotes 5.five.2
388 accurate pop-up causes in “RTTY spot” and “non-RTTY virtual spot” panels to correctly reflect PKT/PKT-R and facts-L/facts-U selections 5.five.3
389 prevents a double-click on within the Spot Database display from being ignored in certain situations 5.5.3
390 the defaults for the pursuit of marathon usa-bands, country-modes, region-bands, and region-modes ought to be disabled, no longer enabled 5.5.five
391 prevent an errorlog.txt access from being generated in SpotDatabaseModule.UpdateProgress five.5.7
392 effectively reposition horizontal positioning when updating the Spot Database show five.5.9
393 correct regression that permits formerly-deleted columns to appear in the Spot Database display 5.6.zero
394 accurate the explanatory popup that appears whilst the mouse cursor hovers over a callsign in the Spot Database display to don’t forget “band sought” and “mode sought” for the DXCC, Marathon, and WAZ awards five.6.1
395 successfully announce wanted CQ zones 5.6.2
306 the Continent clear out’s All and None buttons have to successfully update the Antarctica checkbox 5.6.four
307 nicely update the Spot Database show whilst a CQ area like Kosovo is labored 5.6.8
308 right now re-filter out the Spot Database display after updating development in response to a new QSO being logged five.6.8
309 revert to the sooner implementation of UpdateSpotDisplayRecordsets 5.6.eight
310 ensure that the Spot Database show is right now updated when DXKeeper reports that a QSO has been logged 5.6.8
311 restore the better-overall performance implementation of UpdateSpotDisplayRecordsets 5.6.nine
312 when notified of a logged QSO with the aid of DXKeeper, nicely replace Marathon development if one or extra band or mode certificate is being pursued five.6.nine
313 web Server have to show WAZ and Marathon need coloring five.7.0
314 accurate JT6M container in Mode clear out 5.7.1
315 tell the user while the log record detailed for award checking cannot be opened 5.7.2
316 nicely set the “ModeWorked” spot database discipline for non-RTTY modes that count number for DXCC RTTY awards, and the “CQZModeWB4” spot database field for non-RTTY modes that matter for DXCC RTTY or DXCC digital awards 5.7.2
317 save you a gap whose spot notes contain BPSK or BPSK31 from being improperly highlighted as needed five.7.3
318 nicely handle the case wherein realtime Marathon award monitoring is enabled and a logged QSO with a DXCC entity that consists of CQ nations is modified to specify no location code five.7.4
319 do away with an errorlog.txt entry from WebServerForm.Webserver_DataArrival 5.7.five
320 whilst a spotted station’s DXCC entity or CQ quarter can’t be decided, properly set the spot database entry’s WAZ and Marathon progress fields 5.7.5
321 well show award monitoring for an entry whose DXCC entity or CQ zone couldn’t be determined five.7.five
322 efficaciously re-allow automated scrolling while the Spot Database show is empty, the “Date and Time type order” panel is about to “descending”, and the person clicks the blinking “autoscroll disabled” indicator or the |< button. 5.7.6 323 refuse to begin if an example is already jogging 5.7.6 324 prevent errorlog.txt record entry in SpotDatabaseModule.UpdateProgress, kingdom = five 5.7.7 325 save you a niche database entry from being taken into consideration “wanted for Marathon” if it would not specify a legitimate DXCC entity 5.eight.zero 326 if at some point of startup the spot database pathname specifies a nonexistent pressure, inform the consumer in preference to generate an errorlog.txt file 5.eight.1 327 correct the explanatory popup displayed through the clear out panel’s wanted button 5.eight.2 328 correct a regression in 5.eight.1 that causes Marathon area development to be incorrectly recorded in each Spot Database entry five.eight.2 329 if Realtime Award monitoring for Marathon is enabled, Spot Database Entries which might be verified for DXCC and WAZ and not wished for Marathon are coloured as “confirmed” as opposed to “verified” 5.eight.three 330 save you errorlog.txt access advent through DeleteSpecialCallsignEntryCmd_Click 5.8.four 331 save you errorlog.txt entry introduction by Config.SpecialCallSortCmd_Click five.eight.four 332 whilst DXKeeper logs a QSO with a station, successfully update Spot Database Entries with that station’s DXCC entity and CQ zone five.eight.5 333 while an square filter out is activated whilst the Freq filter out is energetic, save you the Freq clear out from being reactivated while the transceiver QSYs five.eight.6 334 save you an errorlog.txt record entry from being generated by SpotDatabaseUI.DoEnableAutoScrollWorker five.nine.0 335 whilst saving sq. filters to the windows Registry, update line breaks with ; whilst restoring square filters from the windows Registry, replace with line breaks five.9.three 336 enhance the accuracy of very short and really lengthy distance calculations five.9.four 337 while directed to edit an square filter out, robotically display the best clear out financial institution in the square filter window 5.9.4 338 with DXLab configured for Realtime WAZ award monitoring and the digital container checked inside the “WAZ Bands & Modes” panel at the Awards tab of DXKeeper’s Configuration window, well updates a spot Database entry whose CQ quarter is wanted in a virtual mode while the entry’s callsign is worked in PSK31 5.9.five 339 with DXLab configured for Realtime WAZ award tracking and the digital field checked within the “WAZ Bands & Modes” panel at the Awards tab of DXKeeper’s Configuration window, don’t erroneously flag a PSK31 spot as wanted if the spotted station has already been worked in PSK31 5.nine.6 340 accurate regression in QSX extraction added in five.nine.7 5.nine.8 341 prevent a web server port mistakes from producing non-stop errorlog.txt entries five.9.nine 342 put off an errorlog.txt report entry from being created in Config.IRCDisplayColorCmd_Click when the “blunders message” button is clicked inside the IRC sub-tab of the Configuration window’s “Spot supply display” tab 6.zero.zero 343 most effective replace empty outgoing spot notes with “RTTY” if the transceiver’s said mode is RTTY and Commander is running 6.zero.2 344 save you overflow in ClusterModule.ParseNotes whilst a QSX greater than 2,147,483,647 is noticed 6.zero.2 345 compute QTH range and longitude as the center of the specified grid square in preference to its southwest corner 6.zero.three 346 prevent errorlog.txt document entry from being generated in ClusterModule.ParseNotes 6.zero.three 347 do not update DIGI with RTTY in the Award monitoring window 6.0.five 348 add area earlier than frequency in show Spots proper-mouse menu entry 6.zero.6 349 nicely generate an HTML web web page whilst the “Date & Time sort Order” panel is set to Descending 6.0.7 350 if the web server gets “peer is remaining”, reinitialize the internet server so a new request may be time-honored 6.0.9 351 allow square filtering to paintings successfully while Commander is hooked up, but the transceiver has no longer but reported a valid frequency 6.1.1 352 save you an errorlog.txt access from being generated in Config.Form_Load with kingdom=1 6.1.5 353 prevent more than one decimal points from being entered in the Refresh c program languageperiod setting 6.1.6 354 tolerate invalid settings for Spots consistent with page or Refresh interval precise by using the net interface 6.1.6 355 reply to an invalid HTTP command with 410 gone 6.1.7 356 don’t disable and restart the net Server when clearing or pruning the Spot Database 6.1.nine 357 properly sort the Spot Database show after a Prune operation 6.1.9 358 prevent bandspread updates from interfering with the web server 6.1.nine 359 properly type the Spot Database display after a Compact operation 6.2.1 360 after clearing the Spot Database, display the left-maximum column of the Spot Database display 6.2.2 361 after navigating inside the Spot records, show the left-most column of the Spot Database show 6.2.four 362 after invoking the “Set Row peak” characteristic, display the left-most column of the Spot Database show 6.2.5 363 save you automatic pruning from shifting mouse cursor awareness to the principle window’s filter textbox 6.2.6 364 do not car-prune if the pruning c program languageperiod is less than half an hour (.0208333 days) 6.2.7 365 while loading a Sub-band definition document, tell the consumer if any lower-certain or top-sure frequency is faulty 6.three.0 366 re-create errorlog.txt record if it was deleted whilst the utility became walking 6.three.five 366 correct regression in 6.3.5 that sets spot modes to USB and LSB 6.3.6 367 prevent re-access in UpdateSpotRecordsets 6.three.8 368 accurate mistakes in want sq. 6.4.0 369 accurate “Marathon want” description in Spot Database entry tooltips 6.four.1 370 properly update the DXCC award development of PSK31 spot database entries while a brand new QSO is logged 6.4.2 371 if sending a gap thru IRC generates an IRC errors, tell the person rather than create an errorlog.txt file access 6.four.5 372 save you an errorlog.txt access from being created while processing a gap note like “QSX 50100 up” 6.4.9 373 accurate a regression delivered in version 6.4.6 that stops E or W from being entered in the Operator area Longitude 6.four.9 374 prevent wrong characters from being introduced to the e-mail Alarm’s outgoing e-mail cope with 6.5.3 375 prevent e mail indicators from being sent when disabled 6.five.4 376 in web web page generated by means of the net server, show single fees as double quotes in the filter panel textbox 6.5.five 377 in net page generated with the aid of the web server, display unmarried costs as unmarried rates within the filter out panel textbox 6.five.6 378 in net page generated by using the net server, nicely show square filter out buttons for which no caption has been designated 6.five.6 379 dispose of gap in “Audio Alarm” tab’s “Alarm announcements” panel 6.five.7 380 whilst operating from a non-English locale, use period as a decimal separator in spot notes that convey a QSX frequency 6.5.8 381 efficiently decide whether or not a callsign to be added to the unique Callsign listing is just too massive 6.five.8 382 effectively cope with a gap Database entry whose IOTA group, DXGrid, US state, or WPX Prefix is null 6.6.1 383 efficaciously coloration Spot Database Entries while realtime CQ Marathon monitoring is enabled 6.6.2 384 realtime VUCC tracking ought to most effective consider DX stations with accurate grid squares received from spot notes or overrides 6.6.3 385 cast off useless main comma from “not wanted” in Realtime Award monitoring window 6.6.4 386 accurate disorder inside the setting of “worked before” fields for IOTA, VUCC, became, WPX 6.6.4 387 within the “Realtime Award monitoring” window, specify “award mode institution” rather than noticed mode 6.6.5 388 ignores the united states nation decided via a USAP lookup of a callsign that includes a minimize 6.6.five 389 AM and FM count as smartphone for Marathon 6.6.5 390 save you an errorlog.txt entry from being created by using SpotDatabaseModule.UpdateProgress state 7 6.6.6 391 realtime VUCC monitoring must recollect DX stations with grid squares obtained from any source (reverse #384) 6.6.6 392 DXKeeper’s “turned into blended” and “WPX blended” award settings not properly accessed 6.6.7 393 the want field isn’t always efficaciously updated after running a spotted station 6.6.7 394 after CTRL-X in filter panel, audio and e-mail indicators are incorrectly suppressed through Band filter settings 6.6.7 395 prevent errorlog.txt entries in SpotDatabaseModule.RecordSpot states 28 and 30 due to NULLs inside the DXGridSource of Spot Database Entries created by using earlier versions of SpotCollector 6.6.nine 396 save you errorlog.txt entries in SpotDatabaseModule.RecordSpot states 1211 and 3010 due to NULLs inside the DXGridSource of Spot Database Entries created with the aid of in advance versions of SpotCollector 6.7.zero 397 accurate regression in coloring of unique Callsigns 6.7.0 398 don’t announce or ship an e mail notification for a niche Database entry that is hidden 6.7.2 399 efficaciously enforce club Log Leaderboard opposition standards 6.7.3 400 effectively replace a Leaderboard Spot Database access for which a QSO has been logged 6.7.4 401 forget about IOTA tags in spot notes which might be inconsistent with a noticed callsign’s continent 6.7.five 402 successfully replace a spot Database access with a wished US nation for which a QSO has been logged 6.7.6 403 the right-mouse menu “lookup” command need to set off DXKeeper’s major window 6.8.three 404 correctly make bigger sq. filter substitutions like when main or trailing blanks are gift 6.eight.four 405 locate and correct an incorrect recomputation clear out acquired from DXKeeper 11.6.2 or in advance 6.8.four 406 if sending an e-mail alert message fails, retry once earlier than disabling e-mail alerting 6.8.4 407 dont’ generate an errorlog.txt record access if no DXKeeper log is gift, or if “searching for everything” is selected 6.8.5 408 effectively colour Spot Database Entries whose zone-band-mode is needed for WAZ 6.eight.6 409 successfully enforce BandModeAwardSought for WAZStatusString.update 6.eight.6 410 efficaciously set the CQBandModeSought discipline when creating a brand new Spot Database entry 6.eight.6 411 restore font in “colour codes” panel to correct length 6.9.1 412 make certain that that all buttons and panels are seen in the spot supply windows 6.nine.2 413 put off leading and trailing areas from email and server addresses unique on the Configuration window’s e mail tab 6.nine.three 414 don’t forget RTTY as counting for turned into virtual awards 6.nine.4 415 well compute the “sector worked before” subject 6.9.five 415 nicely compute the “sector labored before” field 6.nine.6 416 for changed into award monitoring, consider DC to be MD 6.nine.eight 417 when another SpotCollector window has mouse cursor cognizance, do away with the want to spark off SpotCollector’s predominant window before clicking a button 6.9.nine 418 correctly consist of spot notes in an electronic mail message triggered by using an sq. expression 7.0.0 419 while Commander QSYs, efficiently update its bandspread with spots for the new band 7.zero.1 420 accurate a regression in 419 7.0.2 421 save you an needless errorlog.txt file access 7.0.three 422 when acting a Recompute, best keep in mind VUCC grid squares whose source is specified as legitimate inside the Grid resources for VUCC” panel at the Configuration window’s trendy tab 7.zero.three 423 while a gap Database entry whose grid supply isn’t always legitimate is up to date through a niche that offers a grid source specific as legitimate within the “Grid resources for VUCC” panel at the Configuration window’s wellknown tab, re-examine the access’s VUCC award popularity 7.zero.4 424 save you the addition of a special Callsign list entry whose callsign is already gift on the unique Callsign listing 7.zero.5 425 prevent the advent of special Callsign list entries with null fields 7.zero.6 426 save you an errorlog.txt record entry from being generated by SpotDatabaseModule.GetTags whilst no unique Callsign list is present 7.0.eight 427 successfully get over failure resulting from a horrific square clear out in UpdateSpotRecordsets 7.1.zero 428 efficiently recover from failure in UpdateSpotSortRecordset 7.1.1 429 efficiently type the special Callsign listing 7.1.2 430 whilst growing a niche Database entry, clear the CountryWorked subject in cases where its fee isn’t determined 7.1.4 431 tolerate invalid QSX frequency 7.1.four 432 tolerate excessive QSX frequency in spot notes 7.1.five 433 while determining the probably mode of a DX station from its operating frequency when the station is break up, use the DX station’s transmit frequency, now not its QSX 7.1.6 434 assigns no DXCC entity to callsigns of the shape A/B/MM and A/B/AM 7.1.6 435 prevent Spot Database entry from being taken into consideration for become if DXCC entity is not ok, KL7, or KH6 7.1.7 436 make sure SpotNeed is up to date if it’s far changed while a QSO is logged 7.1.7 437 while a QSO is logged, successfully update the wanted field for DXCC and WAZ popularity 7.1.8 438 correctly update an current spot database entry’s QSX while a “simplex” spot is received 7.1.9 439 correct illness in longpath computation for Azimuth tooltip 7.2.1 440 alternate criteria for determining if a frequency lies within a sub-band from “much less than or identical to the upper sure” to “much less than the upper certain” 7.2.3 441 do away with a redundant lookup directive to DXView whilst double-clicking a spot Database entry 7.2.5 442 save you an invalid square filter whilst putting enter within the Propagation window’s the “DX lively during ultimate 24 hours” panel without a distance specific 7.2.6 443 accurate regression in 7.2.2 that stops acquisition of mode from spot notes whilst enabled 7.2.7 444 correct regression in 7.2.6 that makes a tag column visible inside the special Callsign list 7.2.7 445 if opening the internet server produces a “asked cope with is a published cope with, however flag is not set” error (10013), tell the person in preference to generate an entry inside the errorlog.txt document 7.2.nine 446 save you flicker in Spot Database display heritage coloring when updating Spot Database Entries with an SNR forecast 7.3.three 447 do not provoke an SNR Prediction Request whilst one is already in development 7.three.4 448 disconnect from PropView if an SNR Prediction Request is not fulfilled inside 60 seconds 7.three.four 449 nicely dequeue pending SNR Prediction Requests 7.3.5 450 don’t request SNR Predictions for Spot Database Entries for which a prediction has already been requested 7.three.five 451 well permit SNR Prediction controls 7.3.five 452 ensure that SNR Predictions are up to date hourly 7.three.5 453 do not enqueue SNR Prediction requests whilst PropView is not going for walks 7.three.7 454 when restoring a window’s position with “use a couple of video display units” enabled, properly decide whether or now not the window may be displayed on a physical reveal 7.3.7 455 replace eQSL.wav and zone.wav sound files with documents that designate a codec that may be played on all structures 7.four.0 456 consists of declaration files for DXCC entity-prefixes changed in DXCC Database version 2.five.2 7.four.0 457 restores the “moves with virtual Mode utility connected” panel to the Configuration window’s wellknown tab 7.four.zero 458 take away trailing spaces from the names of bands described within the sub-band definition file 7.four.2 459 ensure that override changes are conveyed to DXKeeper 7.4.four 460 whilst Commander isn’t always going for walks, disable the “QSY to …” command within the Spot Database display’s right-mouse menu 7.four.6 461 efficaciously interprets spot notes of the shape “mode up” or “mode down”, e.g. “RTTY up” 7.4.6 462 restriction the quantity of Spot Database display columns to the number of Spot Database fields 7.four.7 463 whilst inspecting spot notes, don’t keep in mind JT44, JT65,. or MT63 to be an NPOTA park code 7.four.8 464 properly determine the decision place of spotting stations that contain a / of their callsign 7.4.9 465 with IOTA realtime award monitoring enabled, nicely cope with an lively station whose mentioned IOTA tag adjustments 7.five.0 466 correct the tab order within the sq. clear out window 7.five.1 467 efficiently interpret “Heard in XX” whilst it terminates the spot notes 7.five.2 468 well document QSX when spot notes are of the shape ” up” or ” Down” 7.five.5 469 prevent the primary window’s clear out panel caption from being cleared 7.6.0 470 do not set off DXKeeper or WinWarbler till DXView has processed all async prefix lookup requests 7.6.3 471 do not difficulty research requests until DXView has processed all async prefix research requests 7.6.four 472 properly flag the PrefixLookup and GridUpdate directives issued while requesting automated DXView replace 7.6.five 473 save you double-clicking of Spot Database Entries from being locked out while beneath heavy load 7.6.6 474 save you overflow in ClusterModule.ParseNotesForInfo with huge quantity in notes 7.6.7 475 accurate QRA captions in Mode clear out window 7.6.eight 476 prevent errorlog.txt record entry generated through DDEClientModule.SetServerConnected on shutdown 7.7.zero 477 accurate regression added via illness repair 473 that could save you processing of incoming spots 7.7.0 478 when the usage of an sq. filter to manipulate audio or electronic mail announcements from a locale that employs comma as the decimal separator, determine whether or not a new lively DX station must be introduced or emailed with out generating an errorlog.txt record 7.7.2 479 correct regression brought via disorder repair 477 that allows undesired recursion whilst “log debugging info” is disabled 7.7.3 480 defer termination whilst updating a database record 7.7.four 481 on receiving a “startup” DDE message from DXView, wait till that message has been processed to ship DXView plot directives for lively DX stations within DXView’s “lifetime” parameter 7.7.6 482 well interpret DXView’s Spot Lifetime putting whilst it is a fractional price 7.7.7 483 send wanted spots to Commander whether or not they may be at the transceiver’s present day band 7.7.8 484 inform Commander when filtering the Spot Database show with an sq. expression so it could filter Bandspread stations in that case configured 7.7.nine 485 when updating SNR predictions, don’t generate an errorlog.txt file entry when a deleted record is encountered 7.eight.zero 486 efficaciously cope with decrease-case band and mode names within the sub-band definition record 7.8.0 487 accurate a regression in version 7.8.zero that once identifying whether or not to bring a brand new Spot Database access to Commander erroneously considers SpotCollector’s contemporary filtering despite the fact that Commander is configured to disregard SpotCollector’s filtering 7.8.1 488 whilst conveying up to date callsign colorings to Commander, DXKeeper, and WinWarbler, tolerate connection failures 7.8.2 489 bring accurate want status to Commander’s bandspread and spectrum-waterfall home windows for a station wished for a WAZ band-mode 7.8.3 490 includes Scomm model 9.1.12 7.eight.three 491 successfully interpret bandmode.txt file entries whilst being run from a non-US locale 7.eight.7 492 while growing or updating a gap Database access, study and write the SpotNeeded area once 7.nine.1 493 remove errorlog.txt entry: software errors 340 in module SpotDatabaseModule.SpotClusterConnected: manage array detail ‘4’ does not exist 7.nine.2 494 accurate the Spot Database filter history to work well with sq. filters 7.9.3 495 would not do away with ‘S’ from the wanted area of the Spot Database entry of a station whose nation is needed for was when a QSO with a US station from some other state is logged 7.9.4 496 removes replica entries inside the “Spots of” window 7.nine.5 497 prevents an errorlog.txt report access from being generated when analyzing a spot Database entry’s SpotNeeded field 7.9.6 498 if on startup, the Spot Database can not be opened due to a ” no study permission” errors, the user is brought on to terminate SpotCollector and delete the Spot Database 7.9.7 499 earlier than comparing a callsign to the desired Operator Callsign, take away any trailing -# and other characters no longer legitimate in callsigns eight.0.0 500 in the Realtime Award tracking window, successfully decide whether or not or no longer a WAZ sector-band-mode is sought 8.0.0 501 if a gap Database entry with a tab has an unknown band or mode, its SpotNeeded discipline need to incorporate an L 8.0.1 502 while updating a niche Database entry that is “wanted” for CQ WAZ after being knowledgeable that a brand new QSO has been logged, efficaciously update the entry’s wished discipline 8.0.2 503 correct IOTA, WAZ, and WPX want categorization eight.zero.3 504 after being informed that a new QSO has been logged, effectively update NeedCategory area of each affected Spot Database access 8.0.4 505 when updating a niche Database entry that is “wished” for a CQ WAZ area-band-mode after being informed that a new QSO has been logged, effectively update the entry’s needed area 8.0.5 506 accurate the tooltip related to the filter out panel’s need button 8.zero.6 507 prevent faulty GetNeed result when adding the first access to a gap Database 8.zero.6 508 whilst updating a niche Database entry that is “wanted” for a was kingdom-band, became country-mode, WPX prefix-band, or WPX prefix-mode after being knowledgeable that a new QSO has been logged, efficiently update the access’s needed subject 8.zero.6 509 repair the placement of the horizontal scroll bar after executing the “Compact Database” function 8.0.6