In the source code for kconfig_compiler.cpp the function preProcessDefault, it looks like there is no logic to handle entries of type Font. This means that even if the user has not specified code="true" for the default in the kcfg file, it still places the default value string in verbatim, treating it like code. Ideally, it should parse the string as a comma delimited list of parameters to the QFont constructor, or provide some other mechanism to create a QFont from multiple arguments. A related issue is that KConfigLoader (kconfigloader.cpp) simply uses the entire CDATA of the default tag as the first parameter of QFont, thus it is impossible to specify a default size, style, weight, etc. without using code. This is especially problematic when using a scripting language, since the code to set the default must be done manually rather than in the kcfg file. Reproducible: Always Steps to Reproduce: 1. Create a kcfg file with an entry of type="Font" 2. create a default tag for that entry as follows: <default>"Arial",22</default> 3. run kconfig_compiler on the kcfg file (with appropriate kcfgc file) Actual Results: The line that constructs the ItemFont uses a default value of `"Arial",22` (without the back-ticks) Expected Results: The ItemFont should have the default value passed in as QFont("Arial",22)
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand. Thank you for helping us make KDE software even better for everyone!
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Created attachment 155126 [details] attachment-28420-0.html I filed this so long ago I don't really remember the context around it. And I don't really do much with KDE anymore. On Sun, Jan 8, 2023 at 3:45 PM Justin Zobel <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=329233 > > Justin Zobel <justin.zobel@gmail.com> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > Resolution|--- |WAITINGFORINFO > Status|REPORTED |NEEDSINFO > > --- Comment #3 from Justin Zobel <justin.zobel@gmail.com> --- > Thank you for reporting this issue in KDE software. As it has been a while > since this issue was reported, can we please ask you to see if you can > reproduce the issue with a recent software version? > > If you can reproduce the issue, please change the status to "REPORTED" when > replying. Thank you! > > -- > You are receiving this mail because: > You reported the bug.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!