Running v1.3, Manjaro packages The message dialogue when the generated puzzle is lower than requested now appears all on one line, making an awkward and ugly dialogue window Reproducible: Always Steps to Reproduce: 1. Generate a puzzle with a high difficulty (e.g. diabolical) requested 2. Whenever the program fails to generate the required difficulty the message is produced. Actual Results: Ugly dialogue is generated Expected Results: Nicer dialogue with line breaks in the text as in earlier versions.
Created attachment 101234 [details] Example of the bad dialogue
With my installed KSudoku 1.4 on KDE Frameworks 5.44.0 and Qt 5.10.0, I can confirm this bug. However, when I try with the current development version, the dialog text looks nicely wrapped.
I suspect that this has nothing to do with KSudoku itself. My development version has a slightly larger font which might cause the nice wrapping. I tried this on the console to test the wrapping behaviour in general: $ kdialog --msgbox "Hallo alkjs dfklaj sdkfjakldjf kl;ajdfk ljaskfaklsdj klajsdklfj askklasdjf klajsdklfg jaksldfg asdf aksdj kjasdfk lj;askf klasdjf klasjdf asdkfgjkal sjdkfgj aksdjf klasjdf;kl jasdlkq;'j kasdfg" # wraps nicely $ kdialog --msgbox "Hallo alkjs dfklaj sdkfjakldjf kl;ajdfk ljaskfaklsdj klajsdklfj askklasdjf klajsdklfg jaksldfg asdf aksdj kjasdfk lj;askf klasdjf klasjdf" # shows one long line As for this particular ticket, one could try to insert manual line breaks but I am sure this will lead to other problems.
I think this may be a problem in KF5 or Qt5 message box implementation. Maybe report it upstream. Never happened in earlier version of KDE and Qt, except about 15 years ago when ALL messages came out as one long line. So back then I used my own wrapping version of KMessageBox, but no way should that be necessary today.
Should this bug be moved to whatever component contains KMessageBox?
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!
Was fixed fairly soon after reported. Probably maintainer missed closing (or it was fixed as a side-effect).