Created attachment 118141 [details] Screenshot showing the tiny text above the table data information. STEPS TO REPRODUCE 1.Open a database project. 2.Click on a table in the left column of the project workspace. OBSERVED RESULT The centre region shows the contents of the selected table (i.e. "Data" mode). However, the tabs at the top of the table contents that say "Table", "Data", "Design", "Save Record", "Cancel Recent Changes", "Ascending", "Descending" & "Find" are so small, I needed to read them with a magnifying glass! The most recent Handbook downloaded from docs.kde.org don't look exactly like what I am seeing but I think the region I am describing is called the "Opened Database Objects Area" or something like that. EXPECTED RESULT The text in the tabs is big enough to read and/or there is a way to change the text size. SOFTWARE/OS VERSIONS Ubuntu 18.04.2 LTS 64-bit ADDITIONAL INFORMATION
Thanks. I am proposing that we will start reusing the Property editor fonts settings in that toolbar. Would that work for you?
(In reply to Jarosław Staniek from comment #1) > Thanks. I am proposing that we will start reusing the Property editor fonts > settings in that toolbar. Would that work for you? I guess that would suffice as a workaround for the moment. However, it would be a great improvement if such settings were available from within the gui rather than having to edit a hidden configuration file. Also, I wonder if this problem might have something more to do with the fact that I am running this application in gnome rather than KDE. Is there, perhaps, a way to map various settings between gnome and KDE environments that needs to be known and understood?
1. Yes, this is general TODO item. There are more options, unrelated to this issue, and they are all editable in the kexirc file for now. 2. I was close to propose this but KEXI tries to be in no way pushing away from the user's current environment; it shall be felt as native app under GNOME too. We're closer to that than in the past. Thanks for the report also because of that - and feel free to keep posting improvements proposals :)
Moved to 3.2.1 (3.2.0 is frozen already). Note to myself: Solution is in 404454 branch.