Keyboard Shortcuts
ctrl + shift + ? :
Show all keyboard shortcuts
ctrl + g :
Navigate to a group
ctrl + shift + f :
Find
ctrl + / :
Quick actions
esc to dismiss
Likes
- DXLab
- Messages
Search
|
Re: SpotCollector design, DXView screensize
Dave, AA6YQ
It wouldn't be a problem to have it all in one application.
Personally I have no access to a VHF packet cluster so the most I would use would be two or three Netclusters and maybe an IRC cluster (I've never tried one but it seems reasonable to do so). #CQDX is the only way I know of to get spots from DXS, which seems to be the best source overall. And I've met some nice DXers on the chat channel to boot. You really are going to have to start paying attention to Windows resource usage though. With several DXLab applications open, now I often get an "Out of memory" message from Windows. It's not really out of memory, it's out of Windows resources but it means that I have to be very careful about what applications I have open. I'm concerned that adding one more may just be the straw that breaks the camels back. As I have mentioned to you before, CI-V commander is a tremendous resource hog and I can't help but think that there is something in there that is eating resources for lunch :-) >>>Agreed. 73, Dave, AA6YQ |
|
DXKeeper, PropView, and DXView
Dave, AA6YQ
The "lookup last log entry" blemish is fixed, and clicking Lookup (in the
toggle quoted message
Show quoted text
Capture window) now restores input focus to the Callsign textbox. If nothing else shows up for a few hours, I'll release these in DXKeeper 1.2.2 tonight. I'd like to release PropView 1.0.3 and DXView 1.2.7 (with the working title bar clock) to a larger audience, probably via announcement to several DX and propagation reflectors. Any comment on the recent Vertical Time Bar change before I reduce flexibility by adding users? 73, Dave, AA6YQ -----Original Message-----
From: Richard B Drake [mailto:rich@...] Sent: Saturday, April 07, 2001 16:10 PM To: Dxlab Subject: [dxlab] DXKeeper 121 Dave, I have used V121 this afternoon to log several contacts and it seems to be working well now. One thing that seems strange is that after logging a contact it picks up the callsign of the previous contact and puts it into DXView. Not a big deal it just seems odd. I am also appreciating the contest fields this afternoon. When I am serious about a contest, I will set up WriteLog which is specifically designed for contesting and has many special contesting features. But if I am just dabbling with a contest such as this weekends SPDX contest (i.e. if I hear an SP calling CQ contest, I'll call him and give him a contact) the additional contest fields and keeping track of sequence number are very nice. ----- 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. |
|
Re: Updates
Dave, AA6YQ
You can install the latest update.
toggle quoted message
Show quoted text
Dave -----Original Message-----
From: Tom Brouard [mailto:stagehand@...] Sent: Saturday, April 07, 2001 15:34 PM To: Dxlab Subject: [dxlab] Updates Hi Dave, Is it necessary to install each update individually or does the latest one encompass all updates befor it. I am not able to install each update as they become available. Instead, I have to pile them up and do them all at once when I get my "Ham Time". Thank You 73 de KB2VNB 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. |
|
DXKeeper 121
Dave,
I have used V121 this afternoon to log several contacts and it seems to be working well now. One thing that seems strange is that after logging a contact it picks up the callsign of the previous contact and puts it into DXView. Not a big deal it just seems odd. I am also appreciating the contest fields this afternoon. When I am serious about a contest, I will set up WriteLog which is specifically designed for contesting and has many special contesting features. But if I am just dabbling with a contest such as this weekends SPDX contest (i.e. if I hear an SP calling CQ contest, I'll call him and give him a contact) the additional contest fields and keeping track of sequence number are very nice. ----- 73, Rich - W3ZJ www.w3zj.com |
|
Re: SpotCollector design, DXView screensize
It wouldn't be a problem to have it all in one application.
toggle quoted message
Show quoted text
Personally I have no access to a VHF packet cluster so the most I would use would be two or three Netclusters and maybe an IRC cluster (I've never tried one but it seems reasonable to do so). You really are going to have to start paying attention to Windows resource usage though. With several DXLab applications open, now I often get an "Out of memory" message from Windows. It's not really out of memory, it's out of Windows resources but it means that I have to be very careful about what applications I have open. I'm concerned that adding one more may just be the straw that breaks the camels back. As I have mentioned to you before, CI-V commander is a tremendous resource hog and I can't help but think that there is something in there that is eating resources for lunch :-) ---- 73, Rich - W3ZJ -----Original Message----- |
|
Re: Resizing DXView
Dave, AA6YQ
Thanks for your participation, Tom!
toggle quoted message
Show quoted text
Dave, AA6YQ -----Original Message-----
From: Tom Brouard [mailto:stagehand@...] Sent: Saturday, April 07, 2001 13:25 PM To: Dxlab Subject: [dxlab] Resizing DXView 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 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: SpotCollector design, DXView screensize
Dave, AA6YQ
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. |
|
Resizing DXView
Tom Brouard
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: DXView 1.2.6 regression
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 findI 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 halfHmm! 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 |
|
Re: DXView 1.2.6 regression
Dave, AA6YQ
You can enter lat/lon directly; enter an angle (e.g. 24 12'N ) and then
toggle quoted message
Show quoted text
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 > > > > 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
Dave,
toggle quoted message
Show quoted text
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----- |
|
Re: DXKeeper 1.2.1 is available
That's basically it. At one point I thought I saw it clobber an
toggle quoted message
Show quoted text
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----- |
|
DXView 1.2.6 regression
Dave Bernstein
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 |
|
PropView 1.0.3 is available
Dave, AA6YQ
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 |
|
DXKeeper 1.2.1 is available
Dave, AA6YQ
I noted two QSO Capture window defects in the scenario outlined below:
toggle quoted message
Show quoted text
#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 -- 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. |
|
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 |
|
DXKeeper 1.2.0 is available
Dave, AA6YQ
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 -- your online help will be updated by this process. 73, Dave, AA6YQ |
|
Re: PropView
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, youshould be running DXView 1.2.6 -- sorry for not making this explicit. |
|
Re: discussion of DXView and DXKeeper with KB2VNB
Yes, if it's easy to make it configurable, why not? Like you, I
toggle quoted message
Show quoted text
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----- |
to navigate to use esc to dismiss