VarAC Forum

"All of the sudden"TM, VarAC started crashing when I went to send a QSL card which I've done dozens of times before. It turns out that I'd accidently deleted the QSL Card Image. 25/04/2025 04:50:33 - QSL Card - Unable to read QSL card image: C:\Users\KB0US\Dropbox\KB0US QSL VarAC.jpg at System.Drawing.Image.FromFile(String filename, Boolean useEmbeddedColorManagement) at System.Drawing.Image.FromFile(String filename) at VarAC.Form41..ctor(Int32 screen_position_x, Int32 screen_position_y, String qsl_image_file_name_full_path_text, Boolean fade_to_back_at_bool, String my_full_callsign_text, String my_info_text, String callsign_text, String snr_s_text, String snr_r_text, String mode_text, String band_text, DateTime time_datetime, String my_power_text, String message_text, String email_text) Once I figured out what the problem was, the fix was obvious. Ideally, VarAC should at least display a 🤦 out of frustration rather than crashing.

DX Cluster Spotting: VARAC fills wrong frequency for CQs. It fills the frequency you are on, but the CQ is being called for particular slot. Example: The CQ requests to call on slot 13, but the spot is prefilled with the calling frequency: Note that the CQ protocol is confusing, because it QSYs twice, so after a while, they will return to the calling frequency. Ideally, this should be made explicit (specify when the caller will QSY back). But in the meantime, IMHO CQ spots should send the listening frequency not the calling frequency (which VarAC users will understand he will return to after a while).

Bug: There is a text entry bug in the Broadcast message creation window. When too much message text is entered, it wraps around to the beginning of the line and starts overwriting characters. Suggested fix: The UI should detect when the max message length is reached, and handle it gracefully, with an intentional UI design pattern. Scope: Spotted in VarAC 11.0.7