Change font size in output windows?
-
[quote author="Asperamanca" date="1323676394"]So what I'm supposed to do in the meantime? Screw my OS look & feel just so I can work properly with Creator?[/quote]
Not much, I am afraid. At least you might vote for the bug report 6689.
But I am really afraid that the majority of users is happy with using default system font size. I agree with you that forcing me to reset implicit fonts means screwing my OS look & feel and it is as irrational advice as would be suggestion to use glasses. I really do not want to downgrade my Dell Latitude E5620 by setting OS fonts to the size I use for editing.
-
Sigh
Thanks for the sympathy.
As for a workaround: If I really need to read something from the output window, I can still copy it to an editor window, or an external text editor. It's just not very convenient. -
Good news!
Just now I had recieved a responce from JIRA and it seems, that the problem has been solved, see
-
What is current status of the problem?
Is it possible to change font of Qt Creator output windows (compile output, application output)? -
Check the "bug report":https://bugreports.qt-project.org/browse/QTCREATORBUG-1933 referenced above (site has moved;-) for up-to-date status on the issue.
-
If you are interested in a fix, please vote for this bug.
-
How STUPID problem. It pushes me away from editor.
This is how it looks, if anyone find any solution please post.
(i assume that if i let the creator use manually installed libs, i'll have that qconfig..)
!http://www.nardev.org/_temp/qtinterface.png(Qt Problem)!
-
That looks like someone is preaching layouts, but not using them.
-
I find this really annoying as well. With older versions, circa Qt4.7+Creator 2.0, I had code set to one font, and console output used the system font, and it was much more readable.
This new setting where console output and application output use the same font as code editors is really annoying in comparison. This is a basic UI principle: Different function means different typefaces.
Is there any way to move the bug tracker issue up to Creator 3.x? Or is it better to create a new one?