Hello!

I have tested and confirmed the following outstanding UI issues with flrig 2.0.5.49. ?See details of each issue at the end.

== Reset/Cancel loses your original settings: ?Unchanged. ?Cancel does *not* undo the reset.

== Tab Clr does not reset: ?Unchanged. ?Reset does *not* reset Tab Clr

== Automatically-changing foreground text color: ?Unchanged. ?Changing System/Bgnd2 changes foreground colors for *unrelated* elements!

== Configuration tree navigator hard-coded black: ?Unchanged. ?Still hard-coded to black.

== UI does not update dynamically: ?Unchanged, both meter and Configure dialog boxes.

Tim

AD8JL

Details of issues:

== Reset/Cancel loses your original settings

If you enter the Configure/UI/User Interface dialog box, press Reset and then press Cancel, you will NOT get back the settings you had before you click Reset! They seem to be permanently lost. This is annoying to say the least!

== Tab Clr does not reset

When you click on Reset, the Tab Clr setting is not changed back to the default. Only pressing the Tab Clr button resets the color.

== Automatically-changing foreground text color

When you change System/Bgnd2, almost all foreground colors are automatically changed too. What's frustrating is that the foreground text that's changed is NOT the text used for that background!

For example: after a UI reset: change System/Bgnd2 to medium blue. Most if not all of the text now changes to white. The problem is, only a little bit of text is actually on top of Bgnd2. Most are on Bgnd, and now you have white text on light-grey background! And this seems to change multiple foreground colors: at least both Freq Color and System/Fgnd. Oddly, if you click on those buttons, the setting there is still set at full-black. If I go into those settings and simply click OK, I get black again. But if I go into System/Bgnd2 and simply click OK, I get the white back again!

This inconsistency and widespread random change is enough to drive you mad. :) None of this really seems to make any sense. First of all, if we have a control for changing the color, why does the code try to 'do us a favor' and change it behind our back? Sure, if you set the foreground color to the background color you can't read anything. I get that. But if you're going to change foreground colors based on background colors, you should do it only with that actual background color. Right now, change a single, lesser-used background color and your foreground color changes practically software-wide, even though there's at least four differ background color settings!

== Configuration tree navigator hard-coded black

It seems that the tree navigator foreground text color in the Configuration box does not change no matter what. It doesn't change to white based on background color as described above. It uses System/Bgnd2, yet it does not follow System/Fgnd, either. In fact, I can't make it change at all. Seeing as I'm trying to make a dark UI (where the background is dark and the foreground is light), this is a big difficulty.

== UI does not update dynamically

There are several features that do not change their UI settings dynamically. In the main window, most everything reflects UI changes immediately. However, the frequency and meter do not dynamically. In the Configuration box, most things do not change dynamically when UI settings are made. For example, after a UI reset: Open the Configuration box. Open the UI box. Change the System/bgnd to pink. The main window and the UI window immediately reflect this change. The Configuration box does not. Change System/bgnd2 to blue. Again, both the UI and main windows reflect this change. The Configuration box does not. Now, simply click on the title bar of the Configuration window. The left navigator will change at that point (without the text turning white :) ), but the rest of the window will not. You have to either select something else in the Navigator area or close and reopen the window to get it to redraw.

Thank you for your time and attention. I believe that these are the same issues as already covered in the above GitHub link: nothing has changed from my previous writeup. The GitHub link above includes screenshots, which were also previously included in emails to this list. I don't expect you to use the GitHub issue list if you don't want to – I don't expect you to do anything? you don't want to! ? – but I will put this information there as well for future users. It's way? easier for people to find GH resources than old e-mail threads. However, I will continue to work with the project in an e-mail-first manner.

Tim

AD8JL