The five minute mouse timer business is going too far. Long MSK144 qsos over difficult paths, should not require the OP to be chained to the desk.
Several ops are running (on a clear freq), for hours to complete. They aren't sitting in front of the mouse. The developers may not approve of this operational style. but it should NOT be hard coded. It is going to discourage long standing efforts to see a contact to completion. ...and who hasn't wandered around the shack, or even made a bathroom run, in the course of an hour long attempt? Please don't throw the baby out with the bathwater, *unless there is a compelling reason to do so*. Running smoothly on 260 MSK144, no problems noted, but it's early. :-) Thanks for all the hard work! 73, N0AN Hasan On Tue, Nov 13, 2018 at 10:37 AM George J. Molnar <geo...@molnar.tv> wrote: > Congrats, dev team. Running smoothly so far (Mac OS 10.14). > > Not sure I understand the intent of the five minute no-mouse timer. Isn’t > this essentially competing with the watchdog? Not sure of a use case that > requires this second timer. > > Can you elaborate? > > Thanks > > > > *George J Molnar* > KF2T, Arlington, Virginia, USA > > > Please note my new email: George@Molnar.*TV* > > > _______________________________________________ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel >
_______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
