Bug 1444 : add option to change console text size in preferences window
Last modified: 2010-01-24 19:09



Phillip M. Feldman
Assigned To:

Attachment Type Created Size Actions
shows contrasting text sizes image/TIFF 2010-01-24 13:07 5.49 KB

Description:   Opened: 2010-01-24 13:06
When text is written to the screen via `println`, the font is incredibly
small. For those of us over the age of 15, it would be great if there were
some way to increase this. I'd like to attach a screen shot, but there
doesn't seem to be any way to do that.

I'm using processing version 1.0.9.
Additional Comment #1 From Phillip M. Feldman 2010-01-24 13:07
shows contrasting text sizes
Additional Comment #2 From fry 2010-01-24 14:09
I'll mark this as a feature request.

In the meantime you can do it by hand:
+ look for the location of the preferences.txt file, at the bottom of the
preferences window. click the link to open the folder.
+ quit processing
+ copy the line that begins "editor.font="
+ change 'editor' to 'console' in the copied version
+ save the preferences.txt file
+ restart processing, and the font should now be the same as your editor
font, which will be larger
Additional Comment #3 From Phillip M. Feldman 2010-01-24 17:14
I followed your instructions and then restarted processing, but the size of
the text written by `println` did not change. The line that was added to
processing.txt reads as follows:


Is there documentation for the preferences.txt file? (I searched, but was
not able to find any).

Thanks! Phillip
Additional Comment #4 From fry 2010-01-24 17:16
did you quit processing before making changes?
Additional Comment #5 From fry 2010-01-24 17:20
sorry, that doesn't seem to do it.

well, you can edit the line (it's already in there) in the theme.txt file
found in the lib folder of your processing installation directly. just be
careful when editing that file--if you get errors in there processing won't
behave very well.
Additional Comment #6 From Phillip M. Feldman 2010-01-24 19:09
Editing the line in theme.txt did solve the problem. Thanks! Phillip
This bug is now being tracked here.