Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
assignee='https://github.com/terryjreedy'closed_at=<Date2017-10-28.01:03:14.390>created_at=<Date2017-10-24.13:20:40.688>labels= ['expert-IDLE', 'type-feature', '3.7']
title='IDLE: Make font sample editable'updated_at=<Date2019-01-18.03:01:30.788>user='https://github.com/serhiy-storchaka'
Thanks for the patch. Adding the feature is somehow easier than I expected. After moving the sample text to module level, which I considered doing before, saving edits for the duration of an IDLE session turned out to also be easy.
With 11 point Lucida Console, there is room for 5 more lines, without erasing anything, before anything scrolls off the top.
I expect that saving changes across IDLE sessions would be much harder and likely not worth the effort. I think that exploring font choices is likely rare enough that there is little need to do so.
I don't know if saving the changes would be too difficult.
Create a new config file for the text (I think it would clutter the existing config files, but could also add it there).
Load font_sample_text from the config file.
In apply(), write the text back to the config file.
Have a reset button so that the original sample text could be restored at some point? If so, then need to store the original (current) text somewherem maybe a .def and .cfg version like for the other settings? A reset button would also require some screen space from the text frame.
Makes sense. I guess I didn't think of it being frozen because I was thinking of it being more like the Recent Files list, but pre-populated if it were empty. As you said, probably not worth the effort. :-)