+ AA6YQ comments below

Ok that fixed that,  the other item  should the “Sel” button be grayed out?

+ Yes, on the Configuration window's "DXLab Apps" tab, the Launcher's Sel button should be disabled ("grayed out").

       73,

            Dave, AA6YQ

+ AA6YQ comments below

There is no Sites folder?

+ Then something removed it.

+ First, create a Sites folder in your Launcher folder.

+ Second, download the zip archive from 

<www.dxlabsuite.com/Launcher/Sites.zip>

+ Third, extract the the two files from the zip archive into the the Sites folder you just created.

+ Finally, terminate and restart the Launcher.

      73,
  
              Dave, AA6YQ

+ AA6YQ comments below

When I upgraded the Launcher to the latest version 2.1.4 now

                The "Distribution site" field is blank and the down arrow to select the "Distribution site"  show nothing

                The Sel button for the Launcher is grayed out

 

How to fix?

+ In your Launcher folder, is there a Sites folder? If so, what files are present in that Sites folder?

     73,

            Dave, AA6YQ

+ AA6YQ comments below

When I right-click on a spot in SC I get a choice of "Copy to Windows Clipboard". If I chose this for EA1/CT1HIX/P, what is copied is "EA1/CT1HIX/P on 14317.0 in SSB at 7/31/2020 1520Z (EA: Spain)".

Would it be possible to make it if I click on a certain field in the SC window like the Notes to just copy that field?

+ Are you seeking the contents of the most recent spot's notes, are you seeking access to any of a Spot Database Entry's fields?

73,

Dave, AA6YQ

As a review of the Enhancement Logs listed in

<https://www.dxlabsuite.com/download.htm#AvailableReleases>

will substantiate, many of DXLab's most effective capabilities are the result of enhancement requests posted here and then refined
though subsequent discussion. I very much want this process to continue, even though my responses to individual enhancement requests
will sometimes be negative.

I prioritize my "DXLab Development Time" thusly:

1. answering questions posted here by users

2. correcting defects reported here or elsewhere

3. immediately responding to enhancement requests that will benefit a significant fraction of the user community and can be quickly
implemented

4. implementing larger enhancement requests that were appended to one of the enhancement logs when first suggested (e.g. unlimited
overrides, or the ability to replace PSK tracking for DXCC with a digital mode specified by the user).

The need for ruthless prioritization is driven by the notion of "opportunity cost": the time I spend working on development task A
is time I can't spend working on development tasks B, C, and D. If A delivers less value to fewer DXLab users than B, C, or D, then
the "opportunity cost" of A is the delay in generated users-value from B, C, or D; if DXLab were a commercial product, we'd instead
denominate "opportunity cost" in delayed revenue or delayed market share.

My initial prioritization is not always correct. In some cases, I have considered an enhancement request to be idiosyncratic,
generating value for only a small number of users - only to be surprised by a cascade of "that would really help me" messages. Or
subsequent discussion reveals that a generalization of the original proposal would make it useful to many more DXLab ops. For me,
this is the most rewarding part of the DXLab experience: collaborating with the user community to develop applications that are
better than what I could develop by myself. If this process sometimes feels contentious, that's a normal aspect of any engineering
process governed by fixed resources; I'm thrilled with this group's long-demonstrated ability to disagree without becoming
disagreeable.

Proposed changes to a DXLab application's user interface can be particularly contentious, in that what one user considers an
enhancement may be considered a serious regression by other users. Consider the recent proposal to increase the physical size of
DXView's "Antenna Heading" indicator. My first attempt at this resulted in a slight increase in the height of DXView's Info (Main)
window, consuming more screen space; the resulting expressions of displeasure posted here made it clear that this was unacceptable.
Accomplishing the size increase without increasing the Info window's height required implementing 8 variations of the window's
layout, depending upon whether rotator control was enabled, whether the Special Callsign database was being queried, and whether
the GeogMag panel was displayed. While this was conceptually trivial, working out all the details, coding them correctly, and then
testing every case consumed a lot of my DXLab time -- and Salvatore I4FYV still found a case that I mangled. In general, requests to
"promote" the accessibility of one item at the expense of other items can only be accomplished by giving each user the ability to
position all of the items to his or her liking; while not rocket science either, implementing and testing a general mechanism like
this would take a lot of time, and thus must compete with other large enhancement requests as described above.

73,

Dave, AA6YQ

And the patience of a Saint!

Thanks Dave,
I knew i was doing something incorrectly.
Jim Fuller N7VR

+ AA6YQ comments below

Well, I am doing something wrong. I am attempting to place screens on a second screen. I open DXKeeper and move it to the second screen, then close the program. When I reopen it, it comes up on the primary screen. 
Same is true of Launcher, etc.

I know I am doing something wrong, can someone point me in the right direction.

+ Every DXLab application has a "Use multiple monitors" checkbox on its Configuration window's General tab. Have you checked these boxes? If not, check them, and then terminate and restart the applications.

       73,

             Dave, AA6YQ

-- 
Jim Fuller
Montana Section Emergency Coordinator
N7VR -- http://www.n7vr.org
ARRL Life Member
CWOP-2 -- http://www.wxqa.com
Original ARECC contributor

Hmmmm.....let's not forget this is FREE software. 

I think Dave has done a pretty darned good job providing a fine product which does so many things very, very well. Yes, there are changes I'd also like to see. But I balance that with the price I paid.

Ron
N4XD

+ AA6YQ comments below

On Thu, Jul 30, 2020 at 11:57 PM, Knut Meland wrote:

Good words, Dave. Then we have DXLab for housekeeping and daily use and N1MM for contests. I hope the software for daily use with two computers/two operators won't be missed too much. So far we made it with DXBase and a logfile in the cloud. We will try something like that with DXLab.

+ There is no reliable way to have more than one instance of DXKeeper open the same log file at the same time. Please do not attempt this.

          73,

                Dave, AA6YQ

Good words, Dave. Then we have DXLab for housekeeping and daily use and N1MM for contests. I hope the software for daily use with two computers/two operators won't be missed too much. So far we made it with DXBase and a logfile in the cloud. We will try something like that with DXLab.

73 de Knut LA9RY

+ AA6YQ comments below

Well, I am doing something wrong. I am attempting to place screens on a second screen. I open DXKeeper and move it to the second screen, then close the program. When I reopen it, it comes up on the primary screen.
Same is true of Launcher, etc.

I know I am doing something wrong, can someone point me in the right direction.

+ Every DXLab application has a "Use multiple monitors" checkbox on its Configuration window's General tab. Have you checked these boxes? If not, check them, and then terminate and restart the applications.

73,

Dave, AA6YQ

Well, I am doing something wrong. I am attempting to place screens on a second screen. I open DXKeeper and move it to the second screen, then close the program. When I reopen it, it comes up on the primary screen. Same is true of Launcher, etc.

I know I am doing something wrong, can someone point me in the right direction.

Jim Fuller
Montana Section Emergency Coordinator
N7VR --http://www.n7vr.org
ARRL Life Member
CWOP-2 --http://www.wxqa.com
Original ARECC contributor

hmmmm

I guess I shouldn't hold my breath

Thanks Dave

Don