开云体育

The only thing I know abut designing cards is contained in the DXKeeper Help file and the DXLab WiKi - particularly: <https://www.dxlabsuite.com/dxlabwiki/GeneratingQSLCardsBackgroundImage> You could

This is good info Joe. Do you know a way to set the bmp image to a certain size and location on the QSL card? If I use this method to reply to e-mail QSL cards then more than likely I will only have

Hi all, Until recently, I was getting 5 or more electronic QSL's from numerous sources, until I took my email address out of QRZ and put it in my bio with an (at) instead of the @ sign. I did try

Of course, *ALL OF THIS* is moot. DXKeeper already allows one to create and respond to e-mailed QSLs. All that one needs to do is design a QSL card in QSL Config -> Cards. Set the Printer to

Joe, I think you have the best solution. I have been printing the email "telegram" and then hitting delete. Better not to respond in any way. My QRZ page is clear about what I will and won't accept

Greetings to all! The number of Spot Database Entries as shown in configuration spot database tab, does it count *unique callsigns* of spots or not? Is there a way to prune DB by keeping a specific

The damage is done before the delete key can be used. Lacking a "bounce" a commercial e-mail generator can assume the address is, at least, valid. Filters require reviewing anything in "SPAM" to

Joe, W4TV wrote, in part: Perhaps ARRL should provide legitimate bureau staff access to the member directory (with e-mail) ... That would be great, Joe. Unfortunately not everyone belongs to ARRL (and

Thanks for the idea Jamie, I did try that and it only identified the remaining two entities I need, P5 and YK. Dave's link he sent is what I needed.? I'm trying to confirm the DXCC Challenge qso's I

Thank you Dave, Rich - N5ZC

Perhaps ARRL should provide legitimate bureau staff access to the member directory (with e-mail) rather than require amateurs to expose themselves to additional unsolicited commercial (spam) e-mail in

I removed my e-mail from QRZ several years ago (what was there was significantly out of date) and receive very few "electronic QSLs" (a.k.a "spam QSLs"). It also seems to limit the level of amateur

I see a lot of entries w/o bio. There have been lots of suggestions here about handling the electronic/email QSLs. Each has it's merit, and it's an individual choice on how to handle them. From where

Try using the SO2R serial port with O2RSP format. See: ../DXLab/Commander/Help/Configuration.htm (Local copy of the Commander Help file). 73, ... Joe, W4TV

What if one would remove the email address and then put it close to the top of the bio? Would that stop the email cards and still allow bureau workers to get the info? Earl / KD5XB Sent from Proton

+ AA6YQ comments below + When the user selects a Spot Database Entry, SpotCollector sends information from that Entry to DXKeeper, DXView, Pathfinder, and WinWarbler. This is not an extensible

Hi All Looking for some help with a C# program in Visual Studio I am working on where I want to get the callsign from the SpotCollector for the spot that I have selected. The same concept that DXView

+ AA6YQ comments below correct, and wasnt that the original question, how can I determine the 137 thats worked but not confirmed? + The request was to identify the 137 unconfirmed QSOs, not 137

correct, and wasnt that the original question, how can I determine the 137 thats worked but not confirmed?

Juergen wrote, in part: looks as if they all use the email-information given in qrz.com (for sender and receiver of the card). If you take out your email information in qrz. <http://qrz.com/> As a