I second this idea. And, I would add that it would be nice if the decodes were listed by priority (on the left window) with highest priority messages last/bottom in the window. It would also be nice if decodes containing a prioritized call sign as the called party were colored/flagged. Both would help scrolling through a long decodes list during busy times.
Al Pawlowski, K6AVP Los Osos, CA USA > On Sep 21, 2018, at 22:43, wsjt-devel-requ...@lists.sourceforge.net wrote: > > Date: Fri, 21 Sep 2018 18:09:03 -0500 > From: "K5GZR - Rick" <k5...@comcast.net <mailto:k5...@comcast.net>> > To: <wsjt-devel@lists.sourceforge.net > <mailto:wsjt-devel@lists.sourceforge.net>> > Subject: [wsjt-devel] alerts and colors > Message-ID: <000001d45200$17761800$46624800$@comcast.net > <mailto:000001d45200$17761800$46624800$@comcast.net>> > Content-Type: text/plain; charset="us-ascii" > > Users should have the ability to activate/inactivate each of the alerts, in > addition to having the ability to set the color for each of the alerts. > > Inactivating an alert (instead of the current work-around of changing an > alert's color to white) avoids wasting CPU cycles on alerts that are not > wanted by the user. > > Users should also be able to set the relative priority of the alerts based > on their individual importance to the user. > > A priority of zero could be used to specify that an alert is to be > inactivated.
_______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
