Just a suggestion, but it seems a little silly to have to create a new Monitor style just to turn on the option to use a monospaced font in the console. That seems like the kind of option that should be separate from the style, and the style should just have you pick both the fonts to use in each context (normal and monospaced).
The default style uses a monospaced font for the console, so you actually don’t have to do anything.
We tied it in with the style because it’s part of the font configuration. I guess I could see both sides of the argument, but I don’t know if one is necessarily more correct than the other.
Cheers,
Ryan
That’s the thing… it doesn’t. 
At least not in 7.0.2.3. I can see that the greyed-out checkbox is checked for the default style, but the font is definitely not monospaced.
Strange…
Can you post a screenshot of the console window, and let us know which OS and version of that OS you are seeing this on?
Maybe it’s a case of a font not existing…
This is on Fedora 19 x64 using KDE.
Here are screenshots from the default style and a custom style, respectively. I’m confused about how it could be the result of a font not being found, since I didn’t change a single thing about the custom style; I just clicked “Create new style” and then restarted the monitor.
Default:
Monospaced:
Interesting…
We’ve logged this as a bug and we’ll try to reproduce.
Thanks!
Ryan
I was able to reproduce this problem with 7.0.2.3, and it only seems to affect the Reports panels in the Monitor. The Console panel seems to work as expected.
I also discovered that the Console Font option is actually always ignored for custom styles.
We should be able to address both issues for beta 3.
Cheers,
Ryan
Great, thanks Ryan. Out of curiosity, do you have a projection for a possible 7.1 release date? Trying to decide if it’s worth the trouble of going to 7.0 soon if 7.1 is on the horizon.
We’re aiming for around the end of April or early May, which we’re more or less on track for. All the major features we wanted to get into 7.1 are done, so now we’re just focusing on minor features and bug fixes.
Cheers,
Ryan
OK, thanks. And will 7.1 be an in-place upgrade for 7.0, or will it require a fresh repository?
Because it’s a minor upgrade, it won’t require a fresh repository.