Hi Jim and all others
Yes it makes sence
Can the user define Band or Mode ? It should be implemented also
best 73 de Jose CT1AOZ
[EMAIL PROTECTED]
- Original Message -
From: Jim Reisert AD1C [EMAIL PROTECTED]
To: dx4win@mailman.qth.net
Sent: Tuesday, September 02, 2003 9:23 PM
To elaborate on my earlier post, if I have multiple qsos with thge same
station, and try to read from one bamd qso to another, double clicking gets
me a pop up screen that THE QSO DOES NOT MATCH THE CURRENT FILTER. I have
gone into the filter options screen and tried to change the filter there to
At 09:42 PM 9/2/2003, ARS NZ3O (Byron) FM29fx wrote:
When I spot a station, my spot appears (without the
sending station callsign) immediately and doesn't
disappear when the packetcluster spot arrives. So
each one of my spots appears twice if I don't work
the station and log it. I don't think I
Hi Tom
I'm also running v5.03 here.
I've often wished that any Q listed in the Same Call window could
be selected. The way it works now is that you can only select Q's
from there if they satisfy the current filter you have set.
For example, I can set a filter for 3V8BB on 20m. Alll my Q's
Using 6.02:
While helping a friend who had screwed up his .ini file I noticed that I
don't have one in the save directory of 6.02. I do have one in 6.01 which I
have never deleted from my computer.
Is it possible that my 6.02 is using the .ini file of 6.01? The are both in
the Program Files
you can easely write a new one.go to Preferences and File/write ini file .
you can change the path where the file have to be written !
73
marc on4ma
- Original Message -
From: WC7N [EMAIL PROTECTED]
To: DX4WIN Group dx4win@mailman.qth.net
Sent: Wednesday, September 03, 2003 7:15 PM
As others have said, I might want to swap 2 and 3, 4 and 5. So, it must be
a preference setting.
Also, I might not want to see even black spots, much less gray, so would
want to hide them as I do the gray ones.
John, K2CIB
- Original Message -
From: Jim Reisert AD1C [EMAIL PROTECTED]
DX4WIN doesn't directly use the .INI file. It's used to export/import
configuration across different releases. DX4WIN uses the DX4WIN.CFG file which
contains data imported from a DX4WIN.INI file.
73 - Jim AD1C
=
Jim Reisert AD1C, 7 Charlemont Court, North Chelmsford, MA 01863
USA
I doubt that Paul will ever make these colors user programmable for the
priorities. I think the order you laid out for 1) never worked 2) never
worked mode 3) never worked band will satisfy 90% of the DX community. The
unconfirmed mode and band are neat touches, also. Paul spent a period of
Thanks for the feedback. My prior analysis is included at the end for those
who can't remember. I think it was Mel VE2DC who pointed out that there is an
option to highlight unconfirmed new entities as if they are unworked, so #1
changes a little.
Would it be nice to be fully configurable?
The message seems to be that one size doesn't fit all. I know
that I have seen similar things to those reported here. Possibly
it is because I didn't understand the details of how it actually
works, but I found stations I wanted to work way low down in the
priorities (i.e. my priorities did not
I'm good with this.
At 04:02 AM 9/3/2003 -0400, you wrote:
The priorities I suggested earlier seem to embody these requirements:
1 = never worked
2 = never worked mode
3 = never worked band
4 = unconfirmed mode
5 = unconfirmed band
Does this make sense to everyone?
When using a 756 Pro II the information in the Band window jumps between =
SAT and the Band the radio is on. Also the frequency read when I key =
control R sometimes is correct and sometimes it is in error. Occurs on =
all bands. For example it read 2,129,440 KHz when the true frequency was =
Go into your transceiver settings and set CT-17 TRANSCEIVE to OFF.
73 - Jim AD1C
At 05:53 PM 9/3/2003, Edgar Brown, N6OU wrote:
When using a 756 Pro II the information in the Band window jumps between
SAT and the Band the radio is on. Also the frequency read when I key
control R sometimes is
14 matches
Mail list logo
