As a follow-up, are you using any sort of custom GTK *theme*? Even on a different OS, the resulting elements I think should look reasonably similar and your screenshot certainly appears different in several respects.
What happens if you try running GnuCash without the custom GTK CSS file to see if there is a difference? If you find an improvement, maybe revert the changes in a custom GnuCash CSS file, or else move the previous changes to a custom Gramps CSS file if that is possible with that app so GnuCash runs with the default. Regards, Adrien > On Jun 2, 2020 w23d154, at 2:52 AM, Adrien Monteleone > <adrien.montele...@lusfiber.net> wrote: > > Thanks, that is interesting. > > I can’t see from the GTK CSS file rules you listed that they would adversely > influence radio buttons. > > It is possible, that a font choice *might* but if so, that would definitely > be a GTK bug. Rendering and visibility of such UI elements should be > independent of font selection. > > It looks as if there is some sort of over-exposure issue with your display > settings. The top of some elements are variable, particularly the radio > buttons. > > I’ll make an attempt at attaching what I see on MacOS: > > If it comes through, you should see that the non-selected radio buttons are > plainly visible. If your monitor doesn’t look like this, I’d consider making > adjustments because this likely won’t be the only app you’ll have an issue > with if tops of elements are overexposed to the point of not being readily > visible. > > Regards, > Adrien > > <Screen Shot 2020-06-02 at 2.47.17 AM.png> _______________________________________________ gnucash-user mailing list gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user If you are using Nabble or Gmane, please see https://wiki.gnucash.org/wiki/Mailing_Lists for more information. ----- Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
