Hello Guys, Really don't want to get in the middle cuz I'm busy as heck, but...
This was intended to allow you to see the specifics such as beam heading, country, etc associated with a certain spot. The band and mode in the QSO window did not used to change from the default you were using. Somewhere along the line (v6.04?) an addition was made to show the country window, zone window, WAS window stats for these zipping by spots. To do this, the band / mode would show changed in the QSO window. The down side was that it was also changing the rig as well! Not good! We changed this in v 7.01 to keep it from changing the rig, as it should be. The band and mode of the rig should be stable and not change. BTW, as soon as you enter ANY callsign data into the empty callsign field, this viewing of the incoming spot information immediately goes away and it will only show stats for the callsign being entered. 73 de Steve NR4M At 06:23 PM 5/27/2005, you wrote: >Wolf (DL5FU) wrote: > >When adding QSOs in real-time and the QSO window is still empty, each >time a new spot comes up the mode and band are set according to that >spot. The default settings in Prefs|QSO are ignored. >.. > >I concur, Wolf. I've had problems with this issue since v6.03 and had >hoped that it would be rectified in the next major release. It's >essentially impossible to run a casual contest with the packetcluster >active with the mode and band always changing. I would hope that there >could, at least, be some way of disabling this behavior in a future >release. > >Rich Eckman >KO4MR > >_______________________________________________ >Dx4win mailing list >[email protected] >http://mailman.qth.net/mailman/listinfo/dx4win 73 de Steve, NR4M Rapidan Data Systems "DX4WIN... the way logging software should be" Free demo at www.dx4win.com
