| 17 |
When selecting a font face in the User Preferences dialog area for text items, the program aborts. |
G0WDA |
There is a bug in .Net that causes QslDesignAndPrint to crash when it encounters a faulty font file.
This problem occurs only when attempting to display text using the faulty font in certain widgets.
The ComboBox widgets containing font face names used to display the font name in its font face; these
ComboBox widgets now display the font names in the standard widget font face. |
1.6.8 |
Closed (Fixed) |
| 16 |
Call U1AQ identified as not having a QSL bureau. As this is St. Petersburg, it should use
the Russian bureau. |
W6NWS |
W6NWS informed me that Russian authorities have now started issuing Un calls where n is
a digit. |
1.6.6 |
Closed (Fixed) |
| 15 |
BN100 and BV100 are valid callsigns. QslDesignAndPrint claims they are invalid. |
W6NWS |
There are 9 special callsigns in this group (BM100, BN100, BO100, BP100, BQ100, BU100, BV100, BW100,
and BX100). Processing has been added to QslDesignAndPrint to handle these non-standard
callsigns. |
1.6.4 |
Closed (Fixed) |
| 14 |
When printing (or print preview) a card with the QsosBox deleted, program aborts. |
G3UCQ |
Also happens when saving JPEG files for printing |
1.6.2 |
Closed (Fixed) |
| 13 |
FormatException reported when reading a card file. |
SQ5PGJ |
On this single computer with locale "pl-PL", the decimal point is being written using '.'
decimal separator rather than ',' decimal separator
as expected for this locale. When attempting to convert the value from text
to a number, program complains about the '.'. On all other computers using the locale "pl-PL",
value is written correctly.
Have been unable to determine why problem occurs on this single
computer. QslDesignAndPrint has been modified to trap this FormatException and attempt conversion
of value again for locale where '.' is the decimal separator.
Only if this fails will FormatException be reported.
| 1.5.6 |
Closed (Workaround Implemented) |
| 12 |
When editing the text of a text item, the text is not updated on the card and the change
is not saved. |
VK3IFM |
As described in the help files, it was necessary to move the mouse cursor to a location
inside the Text Item Properties panel, but outside the text box and click the left mouse button
for the text on the card to be updated. An enhancement was been provided in QslDesignAndPrint
to immediately update the text on the card as text is changed in the text box in the Text Item
Properties panel. |
1.5.4 |
Closed (Worked as described in help files, but an enhancement provided to simplify) |
| 11 |
After moving card files and images from a computer running Windows XP to a computer running
Windows 7, and attempting to open several of the card files, QslDesignAndPrint aborted. |
N9FN |
Could not duplicate the problem, but did include an enhancement to the program to give the
user the choice of searching for the image file, or deleting the image from the card. |
1.5.4 |
Closed (Not Duplicated, and Enhancement Provided) |
| 10 |
If the Cancel button on the Card Open dialog box is clicked, the program aborts. |
N9FN |
One line of code was misplaced in the program. By placing it correctly, the program does
not abort in this case. |
1.5.4 |
Closed (Fixed) |
| 9 |
Importing an ADIF file causes QslDesignAndPrint to abort. |
KS4I |
The ADIF file contained invalid values for the frequency (e.g. 14.295.4) which generated
a format exception when the program attempted to convert from the input string to a number.
Additional checking has been added to validate the frequency and band information for each QSO
in an ADIF file. |
1.5.2 |
Closed (Fixed) |
| 8 |
Selecting a font size of 16.0 for a text item results in a font size of 160. |
PA0LSK |
Caused by number representation for different cultures. I am surprised that no one has
complained about this until now. |
1.4.6 |
Closed (Fixed) |
| 7 |
Selecting QSOs by Time/Date is not selecting correct QSOs. |
K5EVR |
|
1.4.6 |
Closed (Fixed) |
| 6 |
If no text is available for a number of column headers and other text for the QSOs Box,
the program will error with a NullPointerException when an attempt is made to reload the card.
This will occur if the text is deleted in the User Preferences dialog. |
KC0IFW |
Warning message displayed if user attempts to move out of an empty text field in the
Preferences dialog. If a card contains a text value that is empty, a default value is inserted.
|
1.4.6 |
Closed (Fixed) |
| 5 |
In version 1.4.0, attempting to do a print preview generates an error message. Also,
trying to print cards it says the cards were sent to the printer, but no cards are printed.
This is when trying to print cards with QSO info; blank cards print OK. |
K5RCF |
Number of pages to print was not calculated properly. |
1.4.2 |
Closed (Fixed) |
| 4 |
When sorting QSOs by QSL bureau, QslDesignAndPrin crashes. |
W6NWS |
In 1.2.0, callsigns were limited to having a suffix with a maximum of 4 letters. |
1.2.4 |
Closed (Fixed) |
| 3 |
Multiple copies of left portion of card displayed in Design panel under a number of
circumstances. Also text blurry/unreadable. |
W6NWS |
Probably caused by bad graphics driver. W6NWS has not replied as to whether an updated
graphics driver has solved the problem. |
none |
Closed (Assumed Fixed) |
| 2 |
After print or print preview, card in Design panel contains QSO information that was placed
on the last printed card. |
W6NWS |
|
1.2.0 |
Closed (Fixed) |
| 1 |
Opening any saved card causes "Input string was not in a correct format".
This is a solid error on one computer. |
KI4WKT |
Only reported on one computer. This is related somehow to regional settings in the registry
on the one computer. |
1.2.0 |
Closed (Fixed) |
