Ah, you can quell the text decoded display to revert to the VFO B (which is default, I think). Text decode is not default.
As Don pointed out there's two data items and one peice of UI real estate to show them. Tough decision. When I run split and using the decode to text, the VFO B will revert to the Tx frequency when the decode is idle. As soon as more signal (or noise) kicks in then the decode text overtakes the VFO B as you found. There's not enough visual real estate to show the two pieces of data in the same rect simultaneously. The text-decode is a killer app for the K3, too bad it doesn't have it's own dedicated real estate in the UI. When the decode is running furiously and I want to double check the Tx frequency, I just tap A/B, read it off quickly, and tap A/B again. Or I can just roll VFO B a smidge to make it render.. ______________________________________________________________ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:Elecraft@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html
