Date   

Interesting observation with PathView

Richard B Drake
 

I just worked BX7AA on 21.016. I ran the propagation forecast for
him using the current solar flux of 228 (not too shabby) and it
showed that I should have propagation but it was between the 10%
and 50% MUF lines. I managed to work him but the interesting thing
was that the charts showed that propagation to him on that
frequency should improve over the next two hours and then begin to
drop off. Of course there is no guarantee that he would still be
there in two hours but the message to me was that if I had trouble
working him at this time I should keep trying because the
conditions should be improving. Nice job Dave, this is really
useful!

-----
73, Rich - W3ZJ
www.w3zj.com


Re: PropView

Dave Bernstein <dhb@...>
 

To get full interoperability between DXView and PropView, you should
be running DXView 1.2.6 -- sorry for not making this explicit.

73,

Dave, AA6YQ

--- In dxlab@y..., "Richard B Drake" <rich@w...> wrote:
Robin,

PathView does access the prefix database in DXView. All you should
need to do is have both programs running and when you lookup a
prefix in DXView the resulting Lat/Lon information automatically
appears in PathView. If yours is not doing this then perhaps there
is some problem.

----
73, Rich - W3ZJ

-----Original Message-----
From: RTrebil640@a... [mailto:RTrebil640@a...]
Sent: Thursday, April 05, 2001 5:16 AM
To: dxlab@y...
Subject: [dxlab] PropView


Hi Dave,
Have just started using PropView and it seems to work
well at this
QTH. What would make it very quick to use would be the
ability to
use Country prefixes instead of Latitude and Longitude.
All of that
information must exist already in DXView...is there any
way in which
PropView could access that database?
Robin gw3zcf


------------------------ Yahoo! Groups Sponsor

To unsubscribe from this group, send an email to:
dxlab-unsubscribe@y...



Your use of Yahoo! Groups is subject to
http://docs.yahoo.com/info/terms/



Re: PropView 1.0.2 settings not saved between sessions

Dave Bernstein <dhb@...>
 

Ron, are you still having problems with PropView settings like Power
and TakeOff not being saved between sessions?

Is anyone else encountering this?

73,

Dave, AA6YQ

--- In dxlab@y..., "Ron Eberson" <zx@c...> wrote:
YES HE WORKS DAVE thanks for it.

Is it posible to save some settings like power and wave angel of
antenna?
Also on the fig you can see not the top of the 7 from 17 meters.
Can we change the size of the window from Propview so that you can
see the
both DXView and Porpview on the screen compleet?

Thanks in advance and the time you take for all of us.


-----Oorspronkelijk bericht-----
Van: Dave Bernstein [mailto:dhb@m...]
Verzonden: woensdag 4 april 2001 7:23
Aan: dxlab@y...
Onderwerp: [dxlab] PropView 1.0.2 is available


This release corrects the runtime error occuring on systems with a
locale that doesn't use the period character as a decimal separator.

(Ron, this should correct the problem you are encountering with
1.0.1).

If you already have PropView 1.0.1 installed, you can upgrade by
downloading and running www.qsl.net/propview/PropView102Update.exe -
-
it will update your online help and install PropView102.exe, which
you can then run.

73,

Dave, AA6YQ



To unsubscribe from this group, send an email to:
dxlab-unsubscribe@y...



Your use of Yahoo! Groups is subject to
http://docs.yahoo.com/info/terms/


Re: PropView 1.0.2 settings not saved between sessions

Ron Eberson <zx@...>
 

No dave with the last update all are great no problem.
sorry to tell you not before.

-----Oorspronkelijk bericht-----
Van: Dave Bernstein [mailto:dhb@...]
Verzonden: donderdag 5 april 2001 17:18
Aan: dxlab@...
Onderwerp: [dxlab] Re: PropView 1.0.2 settings not saved between
sessions


Ron, are you still having problems with PropView settings like Power
and TakeOff not being saved between sessions?

Is anyone else encountering this?

73,

Dave, AA6YQ

--- In dxlab@y..., "Ron Eberson" <zx@c...> wrote:
YES HE WORKS DAVE thanks for it.

Is it posible to save some settings like power and wave angel of
antenna?
Also on the fig you can see not the top of the 7 from 17 meters.
Can we change the size of the window from Propview so that you can
see the
both DXView and Porpview on the screen compleet?

Thanks in advance and the time you take for all of us.


-----Oorspronkelijk bericht-----
Van: Dave Bernstein [mailto:dhb@m...]
Verzonden: woensdag 4 april 2001 7:23
Aan: dxlab@y...
Onderwerp: [dxlab] PropView 1.0.2 is available


This release corrects the runtime error occuring on systems with a
locale that doesn't use the period character as a decimal separator.

(Ron, this should correct the problem you are encountering with
1.0.1).

If you already have PropView 1.0.1 installed, you can upgrade by
downloading and running www.qsl.net/propview/PropView102Update.exe -
-
it will update your online help and install PropView102.exe, which
you can then run.

73,

Dave, AA6YQ



To unsubscribe from this group, send an email to:
dxlab-unsubscribe@y...



Your use of Yahoo! Groups is subject to
http://docs.yahoo.com/info/terms/



To unsubscribe from this group, send an email to:
dxlab-unsubscribe@...



Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/


discussion of DXView and DXKeeper with KB2VNB

Dave Bernstein <dhb@...>
 

I have resized DXKeeper already as you had described but I was
running 600
x800 resolution. I have up 1024 x 768 It is a little better. The font
is
smaller but I fortunately have my eyesight. My thought on resizing
DXView
was to use a similar function that you have on the side and bottom of
the
log file in DXKeeper to view the list of QSO's that is too large for
the
window. I have found that I run both DXview and DXkeeper together all
of the
time. When I hear a DX station I type the call sign in DXKeeper hit
enter
then look over to DXView to see where the station is. Then I either
pass on
the QSO or try to make contact. Of course this may change as I do
more DXing
but for now this is the procedure I have gotten into without even
thinking
about it.

That's how I run DXView and DXKeeper as well. Have you tried the
new QSO
Capture window in DXKeeper? It lets you work the same way, but
consumes much
less screen space. The full DXKeeper window need only used when you
query
for previous QSOs with a station, or for general log maintenance
(QSLing,
etc). I can certainly give DXView a resizable border, but the result
would
be to "cut off" information -- there is nothing analogous to
DXKeeper's log
where I can simply show fewer log entries. Maybe there should be two
DXView
window sizes -- "full" (displaying all information as you see it now)
and
"reduced", showing a subset of the information in a smaller window.
What
would you see as the essential fields in the "reduced" window?

I have tried to print QSL cards and have come upon a problem which I
think
is with my printer. I have and HP 550C which is pretty old. When I
tried
printing 2 cards the end of the second card was cut off a little. I
tried
printing the same cards at work on an Epson 740 and had no problem. I
cannot
find a way to adjust the print area with the HP printer. Any
suggestions?

I use an HP 895CSE without difficulty, but am unfamiliar with the
550C.
All I can suggest is to manipulate the Printer Setup options in the
standard
Windows way.

On another subject... I have DSL at work and a cable modem at home. I
use
PCanywhwere to do a lot of file transfer and to check my home weather
station etc. I would love to be able to work my Icom IC-746 from my
laptop
at work. Have you heard of anything like this being done?

That's certainly feasible given the 746's extended CI-V command
set, and
there may well be software out there that supports this mode of
operation.
I'm not aware of any, but you might try posting your question on the
Icom
reflector, or doing some Internet searching with Alta Vista or Google.

By the way, Tom, there's now an email reflector for the DXlab suite
(DXKeeper, DXView, WinWarbler, etc.). I've copied the reflector on
this
message, as your comments and suggestions are quite relevant to the
evolution of these applications. If you care to join, you can do so
via
http://www.qsl.net/dxlab/reflector.htm .

73,

Dave, AA6YQ


-----Original Message-----
From: Bernstein, Dave [mailto:dhb@...]
Sent: Tuesday, April 03, 2001 1:06 AM
To: me2u@...
Subject: RE: Just more stuff.


I have been playing around more with your software and I thought that
it
would be handy to be able to adjust the size of the window for DXview
and
DXkeeper. I think that I would like to be able to fit both windows in
my
monitor so I can view the information easier.

The only way to make the DXView window smaller would be to shift to
smaller fonts; I'm a little reluctant to do that given that I
occasionally
get feedback that the fonts are already too small!

The DXKeeper main window is already resizable in two ways: you can
specify which "panels" are visible (using the checkboxes on the Config
window), showing nothing but the basic QSO information if desired.
And you
can drag the window's lower right-hand corner to control the depth of
the
log display.

I'm not sure what version of DXKeeper you are running, but the
latest
development feature now includes an optional QSO Capture window, which
occupies much less screen space and allows you to capture the key QSO
information. Give it a try and let me know what you think.

What display resolution are you running?
Where do you get the postcard paper to print the QSL cards? I cant
seem to
find them locally.

I use 8.5" by 11.5" card stock, which is available in Staples,
OfficeMax,
or most stationary stores. Card stock is available in
different "weights" --
the heavier the weight, the stiffer the card. Your printer
documentation
should state the maximum weight it can handle.

I'm sure this is a lot of extra work but have you thought
about enhancing the software so that QSL cards can be customized with
pictures, different fonts etc?

Adding the ability to superimpose a bitmap graphic on the card
would be
easy, and is "on the list". Allowing the user to control font
selection,
font size, and font color is also not hard, though the addition of
significantly more "knobs" would require a "print preview" operation.

73,

Dave, AA6YQ


Re: discussion of DXView and DXKeeper with KB2VNB

Richard B Drake
 

I have found that I run both DXView and
DXkeeper together all
of the
time. When I hear a DX station I type the call sign in
DXKeeper hit
enter
then look over to DXView to see where the station is.
Then I either
pass on
the QSO or try to make contact.
I use it that way also Dave. I assume you meant that you type the
callsign into the capture window and hit enter. I would still like
to see it do one more thing when you hit enter on a callsign in
the capture window and that is to automatically do a lookup for
previous QSO's with the station. I really like it when I call a
station and he immediately knows my name from a QSO we had last
year and I like to do the same. The present functionality where
you have to click on the question mark to get the lookup is too
slow. I like to see it immediately.

----
73, Rich - W3ZJ


Re: discussion of DXView and DXKeeper with KB2VNB

Dave Bernstein <dhb@...>
 

I like the simplifying aspect of this proposal -- it eliminates the ?
button to the left of the callsign. The Lookup button would do
everything. But it does mean that every "Lookup" will result in the
full DXKeeper window popping up. For those with smaller screens,
having to iconify it after every lookup may become tiresome.

I could create an configuration setting called "check for previous
QSOs on Lookup", which would let us have our cake and eat it too.

Comments?

Any reaction to the Start button change released last nite in 119?

73,

Dave, AA6YQ

--- In dxlab@y..., "Richard B Drake" <rich@w...> wrote:
I have found that I run both DXView and
DXkeeper together all
of the
time. When I hear a DX station I type the call sign in
DXKeeper hit
enter
then look over to DXView to see where the station is.
Then I either
pass on
the QSO or try to make contact.
I use it that way also Dave. I assume you meant that you type the
callsign into the capture window and hit enter. I would still like
to see it do one more thing when you hit enter on a callsign in
the capture window and that is to automatically do a lookup for
previous QSO's with the station. I really like it when I call a
station and he immediately knows my name from a QSO we had last
year and I like to do the same. The present functionality where
you have to click on the question mark to get the lookup is too
slow. I like to see it immediately.

----
73, Rich - W3ZJ


Re: discussion of DXView and DXKeeper with KB2VNB

Richard B Drake
 

Yes, if it's easy to make it configurable, why not? Like you, I
have a large screen monitor (21") and run it at 1280 X 1024
resolution so screen real-estate is less of a problem for me than
it is for many. With all the DXLab applications up I usually still
wind up with some overlapping windows but try to arrange them so
that the most important stuff is always visible. Perhaps another
solution would be to use a separate "Previous QSO's" window which
wouldn't require any fixed buttons or controls and could be sized
to the users liking.

----
73, Rich - W3ZJ

-----Original Message-----
From: Dave Bernstein [mailto:dhb@...]
Sent: Thursday, April 05, 2001 13:50 PM
To: dxlab@...
Subject: [dxlab] Re: discussion of DXView and DXKeeper
with KB2VNB


I like the simplifying aspect of this proposal -- it
eliminates the ?
button to the left of the callsign. The Lookup button would do
everything. But it does mean that every "Lookup" will
result in the
full DXKeeper window popping up. For those with smaller
screens,
having to iconify it after every lookup may become tiresome.

I could create an configuration setting called "check
for previous
QSOs on Lookup", which would let us have our cake and
eat it too.

Comments?

Any reaction to the Start button change released last
nite in 119?

73,

Dave, AA6YQ

--- In dxlab@y..., "Richard B Drake" <rich@w...> wrote:
I have found that I run both DXView and
DXkeeper together all
of the
time. When I hear a DX station I type the call sign in
DXKeeper hit
enter
then look over to DXView to see where the station is.
Then I either
pass on
the QSO or try to make contact.
I use it that way also Dave. I assume you meant that
you type the
callsign into the capture window and hit enter. I
would still like
to see it do one more thing when you hit enter on a
callsign in
the capture window and that is to automatically do a
lookup for
previous QSO's with the station. I really like it
when I call a
station and he immediately knows my name from a QSO
we had last
year and I like to do the same. The present
functionality where
you have to click on the question mark to get the
lookup is too
slow. I like to see it immediately.

----
73, Rich - W3ZJ

------------------------ Yahoo! Groups Sponsor

To unsubscribe from this group, send an email to:
dxlab-unsubscribe@...



Your use of Yahoo! Groups is subject to
http://docs.yahoo.com/info/terms/



Re: PropView

RTrebil640@...
 

Magic, Dave! I just upgraded my version of dxview to 1.2.6, and now
it works perfectly with PropView. Thanks!
Robin gw3zcf



--- In dxlab@y..., "Dave Bernstein" <dhb@m...> wrote:
To get full interoperability between DXView and PropView, you
should
be running DXView 1.2.6 -- sorry for not making this explicit.

73,

Dave, AA6YQ

--- In dxlab@y..., "Richard B Drake" <rich@w...> wrote:
Robin,

PathView does access the prefix database in DXView. All you should
need to do is have both programs running and when you lookup a
prefix in DXView the resulting Lat/Lon information automatically
appears in PathView. If yours is not doing this then perhaps there
is some problem.

----
73, Rich - W3ZJ

-----Original Message-----
From: RTrebil640@a... [mailto:RTrebil640@a...]
Sent: Thursday, April 05, 2001 5:16 AM
To: dxlab@y...
Subject: [dxlab] PropView


Hi Dave,
Have just started using PropView and it seems to work
well at this
QTH. What would make it very quick to use would be the
ability to
use Country prefixes instead of Latitude and Longitude.
All of that
information must exist already in DXView...is there any
way in which
PropView could access that database?
Robin gw3zcf


------------------------ Yahoo! Groups Sponsor

To unsubscribe from this group, send an email to:
dxlab-unsubscribe@y...



Your use of Yahoo! Groups is subject to
http://docs.yahoo.com/info/terms/



DXKeeper 1.2.0 is available

Dave, AA6YQ <dhb@...>
 

This release adds a "Display Previous QSOs on Lookup" checkbox to the "QSO
Capture window" panel of the General configuration tab. When this box is
checked, clicking the QSO Capture window's "Lookup" button filters the Log
to only display previously logged QSOs with the captured callsign.

While looking at the code associated with the "Lookup" button, I noticed
that the DXCC prefix associated with the callsign would not be updated (via
a DXView query) if some DXCC prefix was already specified. One could always
click "Clear" before "Lookup", but why require the extra mouse gesture? So
in this release clicking "Lookup" always queries DXView (if running) and
updates the DXCC prefix.

If you've already installed DXKeeper 1.1.1 or later, you can upgrade to
version 1.2.0 by downloading and then running
http://www.qsl.net/dxkeeper/DXKeeper120Update.exe -- your online help will
be updated by this process.

73,

Dave, AA6YQ


DXKeeper 1.2.0

Richard B Drake
 

Dave,
Try the following. In the capture window, enter a callsign of a
station that "is" in your log, press enter. All looks fine so far,
does the lookup - great. Now click log to log it. Whacky!! If you
need more detail let me know, but I think you'll see it.

-----
73, Rich - W3ZJ
www.w3zj.com


DXKeeper 1.2.1 is available

Dave, AA6YQ <dhb@...>
 

I noted two QSO Capture window defects in the scenario outlined below:

#19: clicking the Log button failed to unfilter the log

#20: the recorded QSO start time is bogus

Was there something else?

Both above the above defects are corrected in DXKeeper 1.2.1; when no QSO
start time is established (by clicking the Start button), the QSO start time
is set to the QSO end time.

If you've already installed DXKeeper 1.1.1 or later, you can upgrade to
version 1.2.1 by downloading and then running
http://www.qsl.net/dxkeeper/DXKeeper121Update.exe -- your online help will
be updated by this process.

73,

Dave, AA6YQ

-----Original Message-----
From: Richard B Drake [mailto:rich@...]
Sent: Friday, April 06, 2001 18:37 PM
To: Dxlab
Subject: [dxlab] DXKeeper 1.2.0


Dave,
Try the following. In the capture window, enter a callsign of a
station that "is" in your log, press enter. All looks fine so far,
does the lookup - great. Now click log to log it. Whacky!! If you
need more detail let me know, but I think you'll see it.

-----
73, Rich - W3ZJ
www.w3zj.com


Yahoo! Groups Sponsor



To unsubscribe from this group, send an email to:
dxlab-unsubscribe@...



Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.


PropView 1.0.3 is available

Dave, AA6YQ <dhb@...>
 

In the release

- there is no longer a "current time" setting

- when the Prediction tab's "Show Current Time" box is checked, the
Vertical Time Index automatically tracks the current time

- you can drag the Vertical Time Index anywhere within the Prediction
graph; doing so unchecks the "Shot Current Time" box

To drag the Vertical Time Index

1. position the mouse over it

2. press and hold the left mouse button

3. move the mouse left or right

4. release the left mouse button

If you already have PropView 1.0.1 installed, you can upgrade by downloading
and running www.qsl.net/propview/PropView103Update.exe -- it will update
your online help and install PropView103.exe, which
you can then run.

73,

Dave, AA6YQ


DXView 1.2.6 regression

Dave Bernstein <dhb@...>
 

The title bar UTC clock does not function in this release -- I
disabled it while debugging something, forgot to restore it, and
failed to notice its condition during pre-release testing. I'll
correct it in the next release.

Any comments on the proposal to create an alternative DXView window
that consumes less screen space by presenting less information and by
displaying a smaller map? What fields should be retained in this
window?

73,

Dave, AA6YQ


Re: DXKeeper 1.2.1 is available

Richard B Drake
 

That's basically it. At one point I thought I saw it clobber an
existing log entry by changing the time/date and band but when I
tried to reproduce that, I couldn't. Perhaps it was caused by the
failure to unfilter the log. We'll test some more with the new
version.

73, Rich - W3ZJ

-----Original Message-----
From: Dave, AA6YQ [mailto:dhb@...]
Sent: Saturday, April 07, 2001 1:23 AM
To: dxlab@...
Subject: [dxlab] DXKeeper 1.2.1 is available


I noted two QSO Capture window defects in the scenario
outlined below:

#19: clicking the Log button failed to unfilter the log

#20: the recorded QSO start time is bogus

Was there something else?

Both above the above defects are corrected in DXKeeper
1.2.1; when no QSO
start time is established (by clicking the Start
button), the QSO start time
is set to the QSO end time.

If you've already installed DXKeeper 1.1.1 or later,
you can upgrade to
version 1.2.1 by downloading and then running
http://www.qsl.net/dxkeeper/DXKeeper121Update.exe --
your online help will
be updated by this process.

73,

Dave, AA6YQ

-----Original Message-----
From: Richard B Drake [mailto:rich@...]
Sent: Friday, April 06, 2001 18:37 PM
To: Dxlab
Subject: [dxlab] DXKeeper 1.2.0


Dave,
Try the following. In the capture window, enter a
callsign of a
station that "is" in your log, press enter. All looks
fine so far,
does the lookup - great. Now click log to log it.
Whacky!! If you
need more detail let me know, but I think you'll see it.

-----
73, Rich - W3ZJ
www.w3zj.com


Yahoo! Groups Sponsor



To unsubscribe from this group, send an email to:
dxlab-unsubscribe@...



Your use of Yahoo! Groups is subject to the Yahoo!
Terms of Service.






To unsubscribe from this group, send an email to:
dxlab-unsubscribe@...



Your use of Yahoo! Groups is subject to
http://docs.yahoo.com/info/terms/



Re: DXView 1.2.6 regression

Richard B Drake
 

Dave,

I use most of the fields as they are with the exception of region
and time. I would like to see the ability to enter Lat/Lon and
calculate the heading. I monitor the Maritime Mobile Service net
and often boats give their position in Lat/Lon and it would be
helpful to be able to enter that and point the beam at them. I
like the map the way it is but one possibility might be to put it
into a separate window with a button to display it. Then the
control portion of the program would occupy less than half of the
current screen real estate.

73, Rich - W3ZJ

-----Original Message-----
From: Dave Bernstein [mailto:dhb@...]
Sent: Saturday, April 07, 2001 1:48 AM
To: dxlab@...
Subject: [dxlab] DXView 1.2.6 regression


The title bar UTC clock does not function in this release -- I
disabled it while debugging something, forgot to
restore it, and
failed to notice its condition during pre-release testing. I'll
correct it in the next release.

Any comments on the proposal to create an alternative
DXView window
that consumes less screen space by presenting less
information and by
displaying a smaller map? What fields should be
retained in this
window?

73,

Dave, AA6YQ


To unsubscribe from this group, send an email to:
dxlab-unsubscribe@...



Your use of Yahoo! Groups is subject to
http://docs.yahoo.com/info/terms/



Re: DXView 1.2.6 regression

Dave, AA6YQ <dhb@...>
 

You can enter lat/lon directly; enter an angle (e.g. 24 12'N ) and then
strike the Enter key.

Hiding the map is certainly feasible; I'd have to find room for a button
that toggles between ShowMap and HideMap, as use of this function seems to
frequent for the Config window. Interest in the map will also increase once
SpotCollector starts plotting spots there.

In the non-map portion of DXView's window, about half the space is taken up
with control labels and associated whitespace; would an "expert view"
lacking this nicety be a reasonable alternative?

73,

Dave, AA6YQ

-----Original Message-----
From: Richard B Drake [mailto:rich@...]
Sent: Saturday, April 07, 2001 10:46 AM
To: dxlab@...
Subject: RE: [dxlab] DXView 1.2.6 regression


Dave,

I use most of the fields as they are with the exception of region
and time. I would like to see the ability to enter Lat/Lon and
calculate the heading. I monitor the Maritime Mobile Service net
and often boats give their position in Lat/Lon and it would be
helpful to be able to enter that and point the beam at them. I
like the map the way it is but one possibility might be to put it
into a separate window with a button to display it. Then the
control portion of the program would occupy less than half of the
current screen real estate.

73, Rich - W3ZJ

> -----Original Message-----
> From: Dave Bernstein [mailto:dhb@...]
> Sent: Saturday, April 07, 2001 1:48 AM
> To: dxlab@...
> Subject: [dxlab] DXView 1.2.6 regression
>
>
> The title bar UTC clock does not function in this release -- I
> disabled it while debugging something, forgot to
> restore it, and
> failed to notice its condition during pre-release testing. I'll
> correct it in the next release.
>
> Any comments on the proposal to create an alternative
> DXView window
> that consumes less screen space by presenting less
> information and by
> displaying a smaller map? What fields should be
> retained in this
> window?
>
> 73,
>
> Dave, AA6YQ
>
>
> To unsubscribe from this group, send an email to:
> dxlab-unsubscribe@...
>
>
>
> Your use of Yahoo! Groups is subject to
> http://docs.yahoo.com/info/terms/
>
>
>


Yahoo! Groups Sponsor



To unsubscribe from this group, send an email to:
dxlab-unsubscribe@...



Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.


Re: DXView 1.2.6 regression

Richard B Drake
 


You can enter lat/Lon directly; enter an angle (e.g. 24
12'N ) and then
strike the Enter key.
Hmm! I thought I tried that and it didn't work, but I just tried
it again and it does work. I'll bet I clicked on "Go" in stead of
pressing enter.

Hiding the map is certainly feasible; I'd have to find
room for a button
that toggles between ShowMap and HideMap, as use of
this function seems to
frequent for the Config window. Interest in the map
will also increase once
SpotCollector starts plotting spots there.
I hope that SpotCollector is next on your to do list. I find that
absence of that is the major reason that I keep reverting to
Logger. I think that once the bugs are worked out and
SpotCollector implemented this will become my main modus operandi!

In the non-map portion of DXView's window, about half
the space is taken up
with control labels and associated whitespace; would an
"expert view"
lacking this nicety be a reasonable alternative?
Hmm! I don't think id like it without any control labels some of
them could be abbreviated and made smaller. Let's see ....

We don't need the Go button, that could be performed by double
clicking the callsign. Prefix could be abbreviated and that field
made smaller, Country could be smaller. Lat/Lon can be made
slightly smaller, distance can be smaller, grid can be eliminated
(put that in the title bar instead of Lat/Lon), Region and Time
can be eliminated. The DXCC button could be eliminated and become
a tab in the config dialog, help could be reduced to a "?". How
does it lay out now? I'd have to see it. Maybe there are a few
other economies that could be applied without affecting the
functionality.

You already have a Map button there. If the main map were hidden
by default, clicking that button would display it, clicking on the
map itself could toggle between the large scale map and the more
detailed ones. The traditional "x" in the title bar would hide the
map again. How are we doing?

----
73, Rich - W3ZJ


Resizing DXView

Tom Brouard <stagehand@...>
 

Hi Dave,

I have upgrade DXView to 1.2.3 and DXKeeper 1.1.7 and will install the
latest updates as soon as my work schedule calms down. Having the capture
window is exactly what I was looking for. I don't feel a need to have the
option to resize DXview any longer.

I have never used any sort of reflector before and I find it very effective.


Thank You



73 de KB2VNB


Re: SpotCollector design, DXView screensize

Dave, AA6YQ <dhb@...>
 

I hope that SpotCollector is next on your to do list. I find that
absence of that is the major reason that I keep reverting to
Logger. I think that once the bugs are worked out and
SpotCollector implemented this will become my main modus operandi!

>The original spot management design involves several applications:

NetCluster -- obtains spots from Telnet packetclusters

PacketCluster -- obtains spots from VHF packetclusters via a TNC
connected to a com port

CQDX -- obtains DXS spots via the #CQDX IRC channel

SpotCollector -- aggregates and displays spots collected from
multiple instances of NetCluster, PacketCluster, and CQDX

This design makes it possible to simultaneously collect spots from
multiple sources and intelligently merge them into a single database.

I've implemented NetCluster and SpotCollector and have them basically
working. SpotCollector currently lacks DXKeeper's database sort and filter
capabilities, and you can't yet configure the presentation of the database
fields to your taste.

I am having second thoughts about forcing the user to deal with so many
different applications . Realistically, the most anyone will do is run two
or three NetClusters, one PacketCluster, and one CQDX. So I'm now thinking
of packaging these within SpotCollector. While NetCluster, PacketCluster,
and CQDX each maintain a window that monitors their respective source, in
practice one focuses on the merged database display maintained by
SpotCluster.

Anyone see a problem with this simplified packaging?


> In the non-map portion of DXView's window, about half
> the space is taken up
> with control labels and associated whitespace; would an
> "expert view"
> lacking this nicety be a reasonable alternative?
>

Hmm! I don't think id like it without any control labels some of
them could be abbreviated and made smaller. Let's see ....

We don't need the Go button, that could be performed by double
clicking the callsign. Prefix could be abbreviated and that field
made smaller, Country could be smaller. Lat/Lon can be made
slightly smaller, distance can be smaller, grid can be eliminated
(put that in the title bar instead of Lat/Lon), Region and Time
can be eliminated. The DXCC button could be eliminated and become
a tab in the config dialog, help could be reduced to a "?". How
does it lay out now? I'd have to see it. Maybe there are a few
other economies that could be applied without affecting the
functionality.

You already have a Map button there. If the main map were hidden
by default, clicking that button would display it, clicking on the
map itself could toggle between the large scale map and the more
detailed ones. The traditional "x" in the title bar would hide the
map again. How are we doing?

>>>Some good ideas to consider.



Yahoo! Groups Sponsor



To unsubscribe from this group, send an email to:
dxlab-unsubscribe@...



Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.