After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 686266 - Changing the font size before beginning typing does nothing in the Text Tool
Changing the font size before beginning typing does nothing in the Text Tool
Status: RESOLVED DUPLICATE of bug 683011
Product: GIMP
Classification: Other
Component: User Interface
2.8.2
Other Windows
: Normal minor
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2012-10-17 05:47 UTC by avraudys
Modified: 2012-10-17 18:56 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description avraudys 2012-10-17 05:47:47 UTC 
If you use the text tool and create a box in which you wish to type text of a certain font, if you change the font size (from the default of 18 to anything else and then press enter), then click on the text box and begin typing, it will forget your typed in font size, forcing you to select the size 18 text and change the font size again.
Comment 1 avraudys 2012-10-17 06:13:21 UTC 
(In reply to comment #0)
> If you use the text tool and create a box in which you wish to type text of a
> certain font, if you change the font size (from the default of 18 to anything
> else and then press enter), then click on the text box and begin typing, it
> will forget your typed in font size, forcing you to select the size 18 text and
> change the font size again.

in addition if you backspace your current written text (if you make a mistake in a word) all the way back to the beginning, it will revert back to the default font size, rather than retaining your specifically set font size.
Comment 2 Max Mustermann 2012-10-17 18:56:04 UTC 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 683011 ***