I agree it is time for the developers to explain their reasoning about this change. To my knowledge, they have explained all other changes of this sort that have been made, so the fact they have remained silent on this only leads to speculation on our part. That will end badly.
And, in the end, the “feature” will be defeated. Someone will write a bit of code that will implement a “mouse”, or someone will work up a little Arduino device that will impersonate a mouse and defeat the whole thing. This may lead to resentment on both “sides” of this issue. Let’s not have sides, OK? Dave / NX6D ________________________________ From: char...@sucklingfamily.free-online.co.uk <char...@sucklingfamily.free-online.co.uk> Sent: Friday, November 16, 2018 11:36:43 AM To: WSJT software development Subject: Re: [wsjt-devel] 5 minute mouse timeout Hi All I hope this feature does not apply, or can be disabled, for EME operation. Perhaps there is some merit for HF operation, but I can see anything good in this for VHF/Microwave and EME. Standard QSOs may take longer than 5 mins to get established. Also, we sometimes run tests where one station acts as a temporary beacon for more than 5 minutes. 73 Charlie G3WDG > When I made some meteor scatter contacts on 222 MHz using FSK441 I recall > leaving the radio and computer running for hours at a time. I'm doubtful > those qso's would have been completed if the other operator and I had both > needed to interact with our computers every five minutes in order to keep > transmitting. > > 73 > > Mark Spencer > VE7AFZ > netsyn...@gmail.com > > > >> On Nov 16, 2018, at 10:40 AM, WB5JJJ <wb5...@gmail.com> wrote: >> >> This 5 minute mouse timeout is not a problem for me (most of the time) >> as my WD timer is usually set for 5 minutes. But occasionally the mouse >> timer hits before the WD timer does and no alert is issued our sounded >> (JTA setting). >> >> With all the negative comments about this timer, and no comments one way >> or the other from the developers on retaining this useless feature or >> removing it, I'm left in a quandary as to their thought processes on >> this to begin with. >> >> I for one, see no need in it at all. If somebody wants to run without >> human intervention for and hour at full power and blow out their PA's, >> that's their problem, not mine. >> >> I know of no other feature on any radio or software that protects us >> from ourselves, except for the band edge lockouts on many newer radios, >> which saved my bacon many times when chasing DX as a Technician or >> General class licensee. >> >> George >> >> -- >> >> _______________________________________________ >> wsjt-devel mailing list >> wsjt-devel@lists.sourceforge.net >> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.sourceforge.net%2Flists%2Flistinfo%2Fwsjt-devel&data=02%7C01%7C%7C4a67a86a5f4b4c0db37708d64bfb465d%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636779939923261996&sdata=KI9qoLa7bhgfiKOxP8X7CAQmlKehwmV3d%2BUCX6i2M%2Bw%3D&reserved=0 > _______________________________________________ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.sourceforge.net%2Flists%2Flistinfo%2Fwsjt-devel&data=02%7C01%7C%7C4a67a86a5f4b4c0db37708d64bfb465d%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636779939923261996&sdata=KI9qoLa7bhgfiKOxP8X7CAQmlKehwmV3d%2BUCX6i2M%2Bw%3D&reserved=0 > _______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.sourceforge.net%2Flists%2Flistinfo%2Fwsjt-devel&data=02%7C01%7C%7C4a67a86a5f4b4c0db37708d64bfb465d%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636779939923261996&sdata=KI9qoLa7bhgfiKOxP8X7CAQmlKehwmV3d%2BUCX6i2M%2Bw%3D&reserved=0
_______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
