Problem reports are welcome here; sometimes they're the result of a defect in an application, and sometimes they are the result of a deficiency in the documentation. Either way, repairing them makes DXLab better, which is one of the fundamental purposes of this online group.
When you encounter what might be a problem, please don't hesitate to post a report here.?
When filing a problem report, I will better understand what's being reported if you avoid the use of pronouns like "it" or "that", as the words or phrase? they reference are often unclear. Don't worry about being repetitious with words; in problem reporting, clarity and precision are far more important than style.
Also, keep an eye out for the words "see errorlog.txt file ..." appearing in the title bar of a DXLab application that you're using. Unless you enabled "log debugging info" on the application's Configuration window's General tab, those words mean that an error has occurred. DXLab applications do their best to gracefully recover when they detect an error, so you may not notice any misbehavior, but sending me the errorlog.txt file will enable me to analyze that misbehavior and prevent recurrence. Instructions are here:
tnx es 73,
? ? ? ? Dave, AA6YQ
