Fixing the program hangs - is it a priority?

classic Classic list List threaded Threaded
2 messages Options
Dan AE9K Dan AE9K
Reply | Threaded
Open this post in threaded view
|

Fixing the program hangs - is it a priority?

Use the poll to register your vote on whether fixing the long-standing issue of lock-ups on exit or on going to the Config page after the monitor is already communicating with the amp should be the first priority.  

Most users are familiar with resorting to Task Manager, End Process as the not-so-elegant method of closing the monitor (and EEPROM utility) when they don't close properly.

Although this sounds trivial, it's a substantial re-write to accommodate the fact that the .NET framework doesn't provide a means to know whether a serial port I request be closed will (a) be handled gracefully and not hang and (b) provide confirmation that the port is indeed closed.

I made progress toward the resolution in the EEPROM utility and it's multi-threaded model.  
Should the top priority be fixing the program hangs?
Dan AE9K Dan AE9K
Reply | Threaded
Open this post in threaded view
|

Re: Fixing the program hangs - is it a priority?

This issue was resolved in version 1.6.6 (December 2014).