Thanks Ray. I dont usually have this problem, but APCC Pro cannot see that an update is available.
From: email@example.com <firstname.lastname@example.org> on behalf of Ray Gralak <groups3@...> Sent: Monday, May 25, 2020 4:17 PM To: email@example.com <firstname.lastname@example.org> Subject: [ap-gto] APCC Standard v220.127.116.11 and APCC Pro v18.104.22.168
I am announcing the availability of APCC Standard 22.214.171.124 and APCC Pro 126.96.36.199 (links below).
Most of the changes are bug fixes and are itemized here:
APCC - BUG Fix - Tracking rates were not working correctly for the GTOCP3 in 188.8.131.52.
APCC - BUG FIX - Prevent Mach 2 from setting HOME to be anything other than Park 3.
APCC - BUG FIX - The ASCOM driver can send values in exponential notation when the value is near zero. APCC was rejecting this exponential notation.
APCC - BUG Fix - Commands starting with "G_" were rejected.
APCC - BUG Fix - Clear flashing scope view when user clears all errors.
APCC - BUG FIX - Settings were not always being correctly saved.
APCC - BUG Fix - Prevent possible overflow in Meridian Limits Add Point dialog.
APCC - BUG FIX - Horizons - some of the menus did nothing.
APCC - BUG FIX - Horizons - Fixed a number of display bugs and made the displayed data more useful.
APCC - BUG Fix - fixed an integer overflow error that would happen occasionally.
APCC Pro - BUG FIX - APPM - Slew would sometimes fail to appear to complete thus stalling data mapping runs.
APCC Pro - BUG Fix - tracking rate correction was not always saved correctly.
APCC - Improvement - Moved virtual port handlers to their own threads to reduce latency when user interface elements are updated.
APCC - Improvement - In the Meridian Tracking Limits Explorer dialog window, add a button to update Meridian Inclination.