Modifications already implemented

Click here for pending requests

DL1ELY proposals:

• I miss a possibility to have the contest-numbers included in the database, for example when printing QSL-labels "Your number: 598". (Partially avalilable from version 2.1)
• When I delete one entry from the QSL-queue, the selection bar will be reset to the first entry in the QSL-print-queue. For me it would be  better to leave the selection bar on the previous or next entry of the deleted one (Available in version 2.1c)
• It would be great to change the QSL-status DIRECTLY from the callsign-lookup, without explicitly modifying the complete QSO.(Available in version 2.2)
  

DL6ZBN proposals:

• Layout: why did you place the QSL info in the middle of the "workflow"? To me, QSL info is no vital QSO information, because normally you fill out the card after the end of the qso, so I would expect to enter that information as the last action after entering the end time of the qso. The present place "interrupts" the normal process of entering qso data. (Already avalilable from version 2.0g)
• Entering data: when you enter a new qso, why don't you read the last known name/town/locator info if a callsign already exists in the database, and fill it into the appropriate fields? You already do this by reading the last known locator from the records and show it in the "Dist./Bear.". This works so fast (at least for the 500+ qso's that are in the test database, hi...) that it shouldn't cause too much additional overhead to read and insert the rest. (Already avalilable from version 2.0e)
• Auto update function: this is perfect for real time logging, but there is one thing to be aware of. The update cycle should be suspended once you have filled in the callsign. At that time, the qso has definitely started (normally; of course there may be exceptions...), and that start time should be fixed! At the moment, the clock keeps on running and therefore gives me the wrong start time! Why don't you keep the start time fix at that point and update the "Ending time" instead? This would make more sense to me. You might also restart updating the start time, if the user erases the callsign field as a sign that the qso should not be logged with the previously fixed starting time.(Available in version 2.2)
• Non-realtime logging (NO time auto-update): when entering a qso with OK, the start time of the previous qso is kept on the creen for the new qso. This makes no real sense. Why don't you take the END time of the previous qso instead and fill it into the start time field of the new one? This is closer to reality, because qso's "normally" happen one after another (except in groups or nets: there you could imagine parallel qso's; but here you could override the preset and enter your own time...).(Already avalilable from version 2.0g)
• Do you plan to include an import filter for CT by K1EA? I have some thousands of HF contest QSO's logged with it.(Already avalilable from version 2.0g)
• Some people would possibly like to split their logs into, lets say: HF, VHF and up, instead of having a HUGE one. So what do you think about the possibility of using different MDB's for different logs? (Available in version 2.3)
• The QSL fields still don't allow entering a "-" sign in order to show that QSL exchange is NOT INTENDED in this case (for example: everyday QSO's with the neighbour station, with whom I don't exchange cards after 200 contacts. In this case a "-" shows me: "AHA, NO EXCHANGE PLANNED". A blank field only shows that no cards exchanged yet, but not the reason).(Available in version 2.3)

DH6JL proposals:

• How about when I can get the "named" locator in >distance and bearing< with a shortkey ??(Already avalilable from version 2.0e)
• How would it be when there is a warning when i worked a station before ( a ring or a beep) ??(Available in version 2.1c)
• How will it be when there is a key for /P ??? by the way it can be the "-" key or any other perhaps when it is programable...
• Build in a access to a callbook-CD ? i mean when i can edit where the vqlog can find a cd and can tell me what's the name and perhaps the address of the other operator.(Available in version 2.2)
• Creation of seperate logfiles for years or hf & vhf. (Available in version 2.3)

EA2LU proposals:

• Statistics of Locators (Only main square, "JO", "JP", etc).(Available in version 2.2)
• Support the entry of Burst and Pings for MS (and longest reflection) and possible statistic with this data (better days/time, etc) (Available in version 2.3)
• Option to list initial QTH locators by date (Available in version 2.3)

YO4AUL proposals:

• Import from FastLog(Already avalilable from version 2.0b)

EA3BTD proposals:

• When a new square or DXCC entity is worked, indication of the number (For instance G.S ##) (Already avalilable from version 2.1)

EA7KY proposals:

• Callsing field before than Date/Time(Already avalilable from version 2.0g)

EA8AJ proposals:

• When the program is not able to determine the Zone of a QSO, it would be good to have the chance to specify it manually somewhere in the program(Already avalilable from version 2.1)
• I would like to be able to access all the stations in a certain DXCC entity.(Available in version 2.2)

DL8EBW proposals:

• Include the support of his VHF-database in the program (Already avalilable from version 2.0f)
• Built an window which automaticly shows you the last 10 qsos you have made (not open the complete logbook - like browse from end) Can be in same position like the window which shows the award infos or the infos if you worked the station before...(Available in version 2.3)

EA3ADW proponals:

• Include automatically the locator (Already avalilable from version 2.0e)

EA4BAS proposals:

• Control of WAS award ("Worked all states") (Already avalilable from version 2.1)
• To assume by default  a certain type of propagation when importing from URELOC (or other programs which don't support the data) (Available from version 2.3)

GM4JJJ proposals:

• Import from FastLog (Already avalilable from version 2.0b)
• Control of WAS (Already avalilable from version 2.1)
• It would be nice to get a list of total DXCC worked including those that have since been deleted. (Already avalilable from version 2.1)
• Posibility to look up the build in table of stations active on VHF (Already avalilable from version 2.0f)
• The start-time keeps updating while a new entry is open. It should remain fixed once a callsign is entered.(Available in version 2.2)
• It would be nice if the previous (maybe 5?) entries could be kept on screen while a new entry is being entered. (Like a real logbook). Its annoying if you are talking to someone and wnat to refer to a QSO a short while ago (maybe to remember a name or a Locator).(Available in version 2.3)

K1UHF proposals:

• Import from CT (Already avalilable from version 2.0g)

IT9VDQ proposals:

• When the station i am making qso it is present on 40000 locators database, VQLog automatically should put his locator in the locator field. If locator it is not the same in the database, i have the possibility to manually change it. This will speed very much the qso imput. Normally a station have the same locator or, at last, the difference it is only on last two letters of locator. (Already avalilable from version 2.0e)
• Will be very fine in the SUMMARIES, an option that search in the field REMARKS, e.g.: search for "*", or search for the word "HSC" numbers………(Available in version 2.2)
• In the option "browse the logbook" (like a spreadsheet view) and some others it is possible to modify the width of the columns, but when i close Vqlog, the program missed this settings, and i must resetting again the width. It is possible to fix it?(Available in version 2.3)

W5UWB proposals:

• When looking up a given call, the day/month are sometimes reversed. (American version of Windows, with date format of MM/DD/YYYY) (Already avalilable from version 2.0e)

YO4AUL proposals:

• Possibility to zoom in / out certain areas from the maps in order to make it more readable.(Already avalilable from version 2.1b)
• Possibility to import / export QSOs from FASTLOG and LOG EQF (Already avalilable from version 2.0b and 2.0e)
• In the QSL label printing, print label options: to include an option to print labels only for qso already confirmed (qsl
  received)
• Possibility to choose geophysic maps to show mountains, rivers, plains  (What about buying MS-Encarta for that...hi..hi)
• When entering a call sign worked before, the operator details: name, qth, qra loc should be filled in automatically from the previous qso   (Already avalilable from version 2.0e)
• In the option menu to have to possibility to choose only tht frequencies and modes tht you use most often.For example if i never operate in ATV, FAX, SSTV, etc why to have all options all the time so i can get confused. (Partially available in version 2.2)
• The same apply for for the type of propagation ( i have to choose from optioons only those propagation modes tht i usually work) (Available in version 2.2)
• Import possibility from EasyLog  (Already avalilable from version 2.0e)
• If you manually select some QSO to send qsls, the qso's are added to the queue and qsl labels printed but the log is not marked as qsl sent (i selected this option)(Available in version 2.1c)
• In the QSL label printing, print label options: to include an option to print labels only for qso already confirmed (qsl
  received)(Available in version 2.3)

OZ1PIF proposals:

• A quick DXCC summary for all HF bands and for the 5 "old" (80,40,20,15 and 10) bands.   (Already avalilable from version 2.0g)
• It would also be nice to be able to generate a report on longest QSOs by band /propagation (VHF/UHF/SHF only i suppose)(Available in version 2.3)

DF2ZC proposals:

• 1. Import. Could you program a feature with a more general input form, e.g. ASCII-format, like:
  Date Time1 Time2 Callsign Band Mode RSTsnt RSTrcvd LOCATOR Remarks ... (separated by blanks)
  Example: 19981230 18:01 18:02 DL2OM 144 CW 599 599 JO30SN Roland(Available in version 2.1c)
• Moreover, sometimes I make just a few contest QSOs (I don't use TacLog for that small number) the program doesn't accept a QSO-No., so I cannot enter 599001 for example. Could the report field be made some digits longer?   (Already avalilable from version 2.1)

OE9ERC proposals:

• 1.) change the layout of the QSO input screen (see attached file)      He looks for  QTH locator to be more close to the call and rapport fields.     Maybe a second "quick entry" mask which can be selected instead of the current input screen would be fine - in such cases of heavy band openings on 6 or 2m     where contest style operation happens.   (Already avalilable from version 2.0g)
• 2.) provide "quich summary of squares" counting JN,JO,KN,KO............similar to existing counting of squares but disregarding the number(Available in version 2.2)
• 3.) provide "quick summary of US states" (that means that the state should be entered as an additional field or as a keyword in an existing field   (Already avalilable from version 2.1)
• 4.) Expand RST field to allow additional entry of contestnumber(s). Or provide fields for contestnumbers. Erich understands that for real contesting a frontend like Taclog is necessary but for EME contest VQLOG is fully adequate except that the number cannot be entered.   (Already avalilable from version 2.1)
• 5.) this one sounds tricky...: in EME somebody who changes his call or who uses a special call for contest is not counted again for initial contact list. Erich looks for a way to mark these contacts as invalid for EME initial. (Available in version 2.3)

EA8AHH proposals:

• Change the modes ( FM,SSB..etc), to the technical denomination, J3E,F3E...etc...(Available in version 2.3)

PE1OUC proposals:

• Place the locator field just after the callsign or report fields, in contest use speed is important and skipping  the 6 fields to go to the locator takes time...  (Already avalilable from version 2.0g)
  A logical method of entering log data is time(auto), Date(auto), Call, SRST(serial) RRST(Serial), Locator >Next record.
• Allow users to update DXCC country's. Example: 1B0 and 2M are not in the database, it would be nice if i can add them..  (Already avalilable from version 2.1)

M0BOB proposals:

• A field for the Power Output, this is a legal requirement in the UK.(Already avalilable from version 2.1)
• A field showing the QSL manager. It would be good if this could be printed in a prominent position at top of the QSL label so the bureau staff can see it clearly.(Partially Already avalilable from version 2.1)

PE1OGF proposals:

• Quick update QSL status for received QSL cards, where you can type a callsign, get the list with QSO's with that station and just change QSL received status by typing 1 letter B or D than Escape for back and type next callsign. This will make updating QSL Received info much easier.(Available in version 2.2)
• When switching on Automatic date/time it is strange that after you entered a callsign the start time of the QSO still increases every minute. After entering a callsign the time should stop and stay on the time when entered the callsign(Available in version 2.2)
• Posibily to print the logbook only for the QSOs made with a certain callsign (Special callsign, event station, etc.) (Available in version 2.3)
• I have a problem with tracking EME-initials, some examples, PA3FBN changed his callsign to PA9KT, WB5LBT changed to W5LBT, VE3KDH changed to VE3KH VQ-Log says NEW initial. PA0JMV moved to a new QTH (JO21PM to JO21PL) VQ log says NO new initial.(Available in version 2.3)
• Will there be a network version too ?? I have 2 computers in my shack, would be nice if I can use both with the same database..(Available in version 2.3)

G8TNU proposals:

• Could you add a TX power level box as it is part of our licence requirements.(Already avalilable from version 2.1)

ES1RF proposals:

• Did have intention to include the rotor control? If YES, will it support KCT-interface? (Partially available in version 2.2)

3C5I proposals:

• After I queue and print my labels, do I have to go back one record at a time and mark those records as "sent"? I have not been able to find a way to mark them all as sent in the process of printing...(Available in version 2.1c)

F4AZV proposals:

• I would like to know if it is possible to have on the europe map circles of 250 kms for example around our qthlocator to notice the arerage of kilometres for a locator square..(Already avalilable from version 2.1b)

DL2FDX proposals:

• I think the Rig is that necessary that it should have its own collum.(Already avalilable from version 2.1)

K1UHF proposals:

• I wonder if you have considered an address lookup from a QRZ or Buckmaster CDrom for QSL info or even off of their web sites. (Available from version 2-3)
• The one thing the program doesn't keep track of is states, I am trying to work all states and it has always been hard to keep track of them. Most US operators would probably want this and I know most of the worlds EME ops are trying for it also.  (Already avalilable from version 2.1)
• Another thing is it would be nice if the map display had a zoom feature, I really can't read the small grid numbers while searching for new grids on the radio. Most of the time all I would want is East of the Mississippi river on the North American map.(Already avalilable from version 2.1b)

VK6XLR proposals:

• Auto fill-in of Town/Village from existing data.   (Already avalilable from version 2.0e)
• Ability to scroll through the log on the addition page using a wheel mouse.(Available in version 2.3)

PA3HEN proposals:

• In printing sample you can see "my loc:" , but on the printed labels this is not printed, only the locator. It will be nice if there is indeed printed "my loc: JO22LM".(Already avalilable from version 2.1b)
• It will be great if you can select by your self this info which has to become on the label, as well tnx or pse QSL, as per info from log sheet. If this QSL rcvd is empty that it prints PSE QSL and if QSL rcvd is B/D it prints TNX QSL.(Already avalilable from version 2.1b)

• I have a request about QSL printing. Because I have more calls and /MM use or not it should be fine if the call can be printed as well on the QSL sticker. Now I give the call by “remarks” but it is better if the call is given separately so I can use “remarks” for other comments. Maybe it is a option to print “My call” in the same line as “My locater”, and then first “My call”, “My locator”.(Available in version 2.2)

• There is some space left for 4 or 6 more award name’s. could it be possible to make 4 or 6 more award fields? (Available in version 2.3)

• Running the callbook while this is running on harddisk and not from CD. (Available in version 2.3)

• Summaries access by “my callsign”. (Available in version 2.3)

• Sorting possibilities by “my callsign”. I use a few calls and when you visiting an other country you have again a new callsign and when you are mobile in an other country you will have many squares. Will be fine if you can sort by used call (my callsign). (Available in version 2.3)

• Is it possible that you configurate possibilities for choices of printing info on the labels, example:
  • tnx or pse QSL (tnx if QSL received is B/D and pse if received is empty)(Already avalilable from version 2.1b)
  • printing the used call conform the field input(Available in version 2.2)
• I am using 2 calls. It should be nice when I can use 1 log for both calls, when I fill in a call that I can see direct of I worked this station already, nevermind my call. So 1 log and 2 users, and that you can see for both calls seperate the DXCC.(Available in version 2.3)
• Maybe it is possible that you can choose by your self which info you can print or just some more options as fixed labels you can choose out. As used callsign.(Available in version 2.3)

PE1LWT proposals:

• Is it possible to split all the summeries by operating call  i.e. I put different calls in (PE1LWT, T98LWT, 3A/PE1LWT, 4U1ITU) the log.. when i do the summaries I only wanna count the squares/dxcc/etc worked with a specified call(mainly PE1LWT) because I don't count the dxcc's and squares from other countries/squares I worked from. (Available from version 2.3)

DL1KDA proposals:

• For My New QSL Cards i need something changed at an angel of 90 Degrees: (Available from version 2.3)
   
  I Have 4 QSL Cards on one DIN A4 Paper like this:
   
   
   
  *********************************************
  *      QSL1           *        QSL2           *
  *                         *                            *
  *   ************       *     **************     *
  *      QSL3           *         QSL4          *
  *                         *                            *
  *********************************************
  This is should be ONE Din A4 Paper with 4 QSL Kards on it.

OH6KSR proposals:

• Import from OH1AA-log (ftp://ftp.funet.fi/pub/ham/hf-log And there choose oh1aa642.) (Already avalilable from version 2.1b)

EI3IO proposals:

• I'm using version 2.0h. I'd also like the QSO time to be registered on leaving the call sign field.(Available in version 2.2)
• Turning to QSL printing, I've noticed that after deleting an entry in the print queue the list always goes back to the beginning of the list rather than the next QSO entry. That would help in the deletion of multiple QSL cards for the same station!(Available in version 2.1c)

GU6AJE proposals:

• Finally, in the Summaries I have found how to list QSOs by prefix - eg I can do all PA calls, or all PE calls, but is there a way to do all calls to a DXCC? At present I can only get all QSOs to the Netherlands by doing all the different prefixes PA, PB, PE, PD etc. (Partially available in version 2.2)

FA1CIL proposals:

• Charts locators of Africa and South America (Already avalilable from version 2.1b)

G0ISW proposals:

• When I print off the colour map with squares confirmed it is slightly too small to easily read the individual smallest square numbers. Is there any way to print it out larger such as A4? It is approximately half the size of an A4 page at present(Available in version 2.1c)
• Can you create a drop down list for radio & aerial as I am sure that like me other amateurs have different radios for HF & VHF and having to type the different ones each time is repetative & time consuming.(Available in version 2.2)

DG3GAG proposals:

• Is it possible to fit the printout of the euro-squarmap on a DINA4 paper ?? Actual it prints out only ~50 % of DINA4 (of a 210x297)(Available in version 2.1c)
• It would be great, if there would be a possibility to print free in qsl-cards. I mean that users can be create or style a backside of a qslcard  free of size  by using the data of VQlog.(Available in version 2.1c)

PA3HEN proposals:

• Is it possible that you configurate possibilities for choices of printing info on the labels, example:
  • tnx or pse QSL (tnx if QSL received is B/D and pse if received is empty)(Already avalilable from version 2.1b)
  • printing the used call conform the field input(Available in version 2.2)

DL1KDA proposals:

• The Other Question is, if I have the Possibility to create my own Access to the Data. You have there some options, like access by square...... It would be nice that there is a option where i could edit some things like: I want to see all QSO´s where I entered in the Remark field the letters AU. There would be the possibility to make individual access like i need them.(Available in version 2.2)
• Print QSL-cards directly (Available in version 2.1c)

G0ISW proposals:

• Drop down menu for different rigs (I have 3 different radios and frequently change between them, typing out the rig and aerials each time I change is laborious. Others no doubt have several radio/aerial combinations)(Available in version 2.2)
• End time auto option (as start time already has)(Available in version 2.2)
• Map zoom feature (Already avalilable from version 2.1b)

OZ1FDH proposals:

• It should not be possible to enter a callsign without a numerical value-quite often the letter O was typed instead of 0.(Available in version 2.2)

OZ2M proposals:

• It could perhaps be an idea to be able to blank selected input fields, if not needed.It is true that jump sequence can be set, but...(Available in version 2.2)
• Dates conforming with ISO8601 CCYY-MM-DD selectable. Perhaps better to use the OS setting directly.(Available in version 2.2)
• Cluster and mapping to database for new stuff. I am probably not the first one to ask for this :-) (Available in version 2.1c)
• Rotator and rig control.(Partially Available in version 2.2)
• When importing e.g. contest logs Propagation Mode may be assumed based upon below matrix, if not marked in log:

Tropo Aurora Es MS ...

50 MHz DX<1000 km If A RST DX>1000 km/all others or blank?

144 MHz DX<1000 km If A RST DX>1000 km If MS reports

432 MHz...

>1 GHz all is tropo, if DX>2000 then EME

Or prompt user when importing if log contains X-mode. Set up an input filter.
Another way is also to easily be able to edit Prop. Mode in non Prop. Mode set QSOs. (Available from version 2.3)

SM3LWP proposals:

• Import from LOGGER 1.0 by Ulf /SM0LCB (http://welcome.to/logger) directly or from the EDI file generated. (The importation can be made by generating an ADIF file from Logger)

DM1CG proposals:

• There ist no windows to write down the RIG for the serveral bands..Or we  haven´t find it. In the moment i must very write down the RIG , if i made an band switch.. not the best solution.(Partially available in version 2.2)

OH5YW proposals:

• Is it possible to have Ulf's SM0LCB fine Logger loggin software called Logger files imported into VQLog? Many users here in finland and sweden would like that possibility (The importation can be done exporting from Logger in ADIF format)

F6ETI proposals:

• Possibility to see in the log screen the last 5 or 10 entries..(Available in version 2.3)

H44PT / G8BCG proposals:

• When accesing to logbook by square I could type say, "IO" and get a list of all QSOs in that field.(Available in version 2.2)

9H5IP proposals:

• When updating recieved qsl card and it is the first confirmation for that dxcc an alert comes on like when you are entering a qso. (Available in version 2.1c)
• Make it possible that the world map icon is active also when the callsign is entered ( without the locator) to have a view where the country is.(Available in version 2.3)

KM5ES proposals:

• I was wondering is there any way to convert the mileage on the right part of the log  from kilometers to miles.ç(Available in version 2.1c)

EI3IO proposals:

• Is it possible to have a flag option which indicates that previous QSO's have been made with the station when the call-sign has been entered in addition to the default DXCC bearing etc info. Then one could go to the QSO flag and retrieve the information. (Available in version 2.1c)

W7YYY proposals:

• I would like to see a "Satellite" field, maybe near the "Propagation" field.  A pull-down would be fine, but it should have the capability of accepting user input, either through option menu access or directly on the input form.(Available in version 2.3)

PA3GST proposals:

•  It would be very nice when entering the table qsl manager, the call will be put into capital letter directly. (now I have to do this by using the caps lock or shift button)(Available in version 2.2)
• Since my start on 6 mtr, I started to count the major squares aswell (KP,JO,IL etc.). Is it possible to add that to the summaries function ?(Available in version 2.2)

PA3GST proposals:

• Your program is not supporting a free label design and also not saving the printing data to a file. I am using BV-label for labelprinting by DF3CB (www.qsl.net/df3cb). This supports ADIF format for input. Would it be possible to add a function to store the whole data of the QSOs to be printed to a file???(Available in version 2.1c)

M0BKG proposals:

• There is one thing that stops it from being legal for use in the UK, the power output is not printed on the LOGBOOK PRINT.
• I would also like the END TIME to auto set on hitting OK to enter the record.(Available in version 2.2)

G0RUZ proposals:

• Rotator control using the ARSWIN, by EA4TX(Available in version 2.2)

K0GU proposals:

• The FCC is now issuing new hams KG4 calls with three letter suffixes (KG4AAA, etc). The program counts all these as Guantanimo. It also counts US calls like NG4C and KG4W as Gitmo. This is quite a problem here in the US. It is my understanding that the military issues ham calls for Gitmo and they are all 2x2 callsigns (KG4AA, etc). It would be helpful if the program counted only 2x2 KG4 prefix calls as Gitmo or if that is a problem perhaps all KG4 calls as the US.(Available in version 2.2)
• Worked KH6ND/KH5 a few weeks ago. The program didn't know what country he is in.(Available in version 2.1c)
• Is there any way to tell the program that W5LBT is the same initial as WB5LBT? (Available in version 2.3)

G0MVP proposals:

• Search for a text in the "remarks"(Available in version 2.2)

HB9CRQ proposals:

• It would be great if it was possible to print maps with only the big squares worked: if I worked JN47 then JN is marked as worked, not the small JN47.(Available in version 2.2)

PA3FYG proposals:

• In the summaries, Extra selection: my callsign or my country: When I move to another QTH in the Netherlands or work /p,
  it still counts for the diplomas when I am out of my square (JO22). I do not want to count my OZ/PA3FYG ON/PE1GTE or 9H3AAL activity. (Available from version 2.3)

DK1CM proposals:

• When importing TACLOG-files the QSO-numbers are not importet. Why not? Usually all QSOs done with one Rig so it would be very nice to import the Rig I used in contest. Maybe also setting the propagation mode.....(Partially available in version 2.2)
• QSLing: I allready told you that it is quite important for me to print the QSO-data directly onto the cards. Therefor an export in ADIF-format would be the easiest solution. That I can use the "label" buttons it would be the best to export the "qsl queue".(Available in version 2.1c)
• If a QSL-label is printet though the label button there is no option to set the flag that the QSL-card is sent via bureau of directly. So if you are using this way you don't know what cards you allready sent if you don't change it manually.(Available in version 2.1c)
• It would be usfull to have a table of some 30 or 40 different Rigs what you can choose for input in the field Rig. So you don't have to write the whole thing very time you QSYed to another band.(Available in version 2.2)
• Further I am missing rainscatter (rs) as propagation for 10GHz (Available in version 2.1c)
• Real time logging: beginning time should stop if I put in the data..... and ending time should be the time when I press return to
  store the data(Available in version 2.2)
• I just tried the new feture to export the data for QSL-printing into ADIF. I am missing the power, rig info and own callsign in this exportation!  Could you please add this??  (Partially available in version 2.2)
• specific exportation in ADIF-format. e.g. all QSOs from date to date. all  EA-calls, all not confirmed QSOs´for further use in an external Program. (Partially Available from version 2.3)
• Exporting RIG and ANT-position for QSL-printing
• Could you make it possible that you can choose the callsign used when you print cards?? Quite difficult if you have to remember the correct date for every expedition or contest activity (Partially Available from version 2.3)
• Another flag for QSLing would be also usefull. Either you want to send a card or not. For example I am only interested in sending card for new squares. All the others I am just answering. If I do a input when entering the QSO that I want to QSL this contact 100% would be very fine. To add a Y (yes) a N (no) or maybe a YB (yes bureau) a YD (yes directly) and N (no).(Available in version 2.3)
• I think there is not much sence to send everyone a card for the 20st QSO on same band and mode...... You are doing a summerie of "initials". It would be great to have a option to QSL every initial! So to say every new station on that band and mode.(Available in version 2.3)
• QSLing to initials only (now only to all not sent already or all not sent back already(Available in version 2.3)

PA3BZL proposals:

F6ETI proposals:

• QSL label printing:   If i work in /P, /M or in a other country (OE/F6ETI) this info is in the main  table (Log) but can not automaticaly print on the QSL labels. Only the  QTH locator can reported on the QSL.  Then,  i suggest that the "IndUsado" field are included in the "ColaQSLs"  table (and in the label models).(Available in version 2.2)

M1CNK proposals:

• When log files are imported from Taclog, would it be possible for the contest serial numbers to be appended to the signal reports?  Whilst I use Taclog for contests, my primary log is VQ Log and it nice to be able to quote serial numbers when trying to get a QSL card from a contest station.(Available in version 2.2)

IK4DRY proposals:

• Creed that the Browse formality is surely essential in the his double function (BEGINNING and END file). But he you would be it even more if it there is the possibility of cancel a QSO from the list directly, if he is written evil, or accused for mistake, and only after through that function, that is used for check attentively. Thease results very hard-working CANCEL a datum, while like other programs; Click above the QSO with the RIGHT KEY of the MOUSE would be enough and make open the MENU with the varied possibility DEL, MODIF, MOVE, COPY, PRINT, etc. etc....(Available in version 2.2)

KA8OCN proposals:

• I was looking for a way to make a note that I had QSLed via eqsl. I can place a B for Via Bruo or D for Direct, it will not even let me type E for Eqsl.(Available in version 2.2)

N9LF proposals:

• Support of MDY format for dates(Available in version 2.2)

G4BVE proposals:

• Add option in QSL sent/received fields of "E" for electronic. For use where a QSL is received/sent via eQSL.cc or via email.(Available in version 2.2)
• The option to store the mode in J3E, G2B etc. format would be useful.(Available in version 2.3)

SM7AED proposals:

• I miss the possibility to calculate the full QTH locator from a given longitude and latitude. I also miss the possibility to calculate the direction between two QTH locators. (Available from version 2.3)

S51TN proposals:

• On export to ADIF is needed some filters, for instance: from date to date, or from QSO Nr to QSO Nr, only one band and so on. I hope it will be soon in the program (Available from version 2.3)

KD5IUG proposals:

• Any luck on getting a link with QRZ and/or Buckmaster data? (Available from version 2.3)

M0ELS proposals:

• Could you put in some satellites ... ie uo-14 , then the uplink and dnlink freqs will be automatically displayed.perhaps you could also add a list of sats to choose from ....with the relevent frequencies...(Available from version 2.3)

N3ZLL proposals:

• Any chance for a "Satellite" field on the future? (Available from version 2.3)

F1ISJ proposals:

• An idea for a next version is to make a box to put the satellite name or better an access table of the satellite used by the ham with the satellite name, the mode of the satellite and the up and down frequencies corresponding to the mode. Example:
  RS10-A-145.880-29.380 and if possible the mode (SSB,CW,FM,SSTV..) RS10-T-21.180-145.880 RS10-K-21.180-29.380
  
  The user of your program have just to choose the name and the mode of the satellite in the satellite name box  and the frequencies are automatically added by VQLog.(I always put the centered frequencie of the satellite because during the QSO, the up and down frequencies change every 5 seconds for the 70cm with the doppler).The user can edit this table in the configuration to add the satellite which he often use. (Available in version 2.3)

F4BAH proposals:

• Possibility to change the background color of the box of the label when printing the QSL, or even make it transparent (Patially available from version 2.3)

NW7U proposals:

• An additional update could be saving to file in the ARRLs required Cabrillo format. (VQLog 2.3 can import Cabrillo files, but saving the log in that format is not meaningful as it is intended for contest programs only)

DJ8MS proposals:

• Another idea I have is connected to the importing of contestlogs. In my case the import from TACLOG...
  If I import contests to vqlog then all qso will have no information in the mask about POWER, RIG and PROPAGATION.
  Could there maybe any small mask useful before importing the qso, when the user puts in the rig, pwr and propagation. In the case of having different propagation, like here sometimes Tropo and Aurora or Tropo and ES or something like this.. then the user have to put this by hand , but in a 'normal' contest there's I think only one propagation. (Available in version 2.3)

KB9WXO proposals:

• Add a field with a drop-down list for Satellites.  It would be nice to also include the communications mode for the satellite contact. (Available in version 2.3)

SP2DDX proposals:

• Include the option of accepting "type of propagation" parameter in ASCII import (Available in version 2.3)

SM4XIH proposals:

• I´m just made som qsl-printing and I found out that it would be nice to mark qso:n that not shall be send qsl. in my old logging-software I put an "-" in the fileld for qsl so the program understood that it NOT gonna get some qsl-card, also for them that allredy have been sent qsl to(Available in version 2.3)

KD5IUG proposals:

• Could there be a code for "QSL Sent Via" to indicate you don't want to send one - such has a repeat contact or grid you have worked 3 dozen times. How about an "R" for repeat contact and/or "N" for no send for the field to block printing.(Available in version 2.3)

9H1PI proposals:

• Summery of longest dx with fiters of band and date from to(Available in version 2.3)
• When entering the call( not the locator ) the world icon would work giving an apprximate (middle) position in the country(Available in version 2.3)

PE1AHX proposals:

• Another thing I would like to see in a future version is an option to place the datafiles in a location of my own choosing instead of in the program directory.  I have started using WinXP with 4*100Gb harddrive & I would like to be able to separate userdata from programs for backup purposes.  I do not want to have to 'find' the files that need to be backed up,  I want to be able to backup an entire datafile backup on a different harddrive.  Maybe something you can do in a next release?(Available in version 2.3)

ES2NA proposals:

• When I use my computer for many callsigns (ES2WX,ES2X,ES8X) then I want use only one AddressBook, VHFDatabase e.t.c.(Available in version 2.3)

DJ8MS proposals:

• Under   Print    QSLs/QSL labels   there comes the window for selecting the dates, modes ,...
  There is also the possibility for checking wether just a qsl was sent or not. These seems only to work for just even this qso.
  Might it be possible to check also wether anywhen just sent any qsl (for this propagation or mode)... For example during the Nordic Activity Contest or just any other contest I always work a lot of stations again and again, but of course I don't want to send them a qsl again.
  Maybe there could be a different button for that perpose?(Available in version 2.3)

KA1A proposals:

• The Ø does not print in the print log but prints as 0.(Available in version 2.3)

KB9WXO proposals:

• Allow a QSO to be marked as "Do Not QSL",  I work a number of satellite stations repeatedly and don't want to send a QSL each time.  I also don't want to send a  QSL if I have already confirmed that Grid, State, etc.  It would nice to simply mark a QSO as no QSL needed.

SM7FJE proposals:

• If you scroll the log and fit the columns to your personal size >>>> they should stay that way until you change it yourself (not back to default)(Available in version 2.3)
• A map over worked/confirmed/pending major fields(Available)

Share:

Home page

Site map

Radio Sherlock search engine

Join the Mailing List !