For some reason, if I change the font in the scheme config, sometimes it completely stops working and reverts to Arial. I can't fix it even between instances.
I'd say this is a bug. Any idea?
For some reason, if I change the font in the scheme config, sometimes it completely stops working and reverts to Arial. I can't fix it even between instances.
I'd say this is a bug. Any idea?
This started happening to me today, too. After playing around with it I found that switching the font to Lucida Console or Courier New both work, but every other font I tried just shows up as Arial.
Hmm I haven't come across this one before. What version are you using?
I'm using v2.0.7.610-devel
Same here.
Looks like disabling the indentation guides triggers this, at least in version 2.0.7.619-dev.
Thanks - I haven't been able to reproduce so far so that will help. It's worth pointing out that there has been lots of code change in the schemes stuff for 2.0.7 so I was surprised I hadn't seen any problems before now!
Hmm, I just noticed that earlier today. I was trying to tweak my font/color settings and the font kept getting screwed up. I think it has to do with a bug in the default charset preference. Here's how I can reproduce it:
1) Open options/defaults; set character set to default. Close options.
2) Open options/defaults again. Character set has reset to ANSI. Close options.
2) Open options/defaults again. Character set is now *blank*. Close options.
That should switch it to a proportional font (Arial?). To fix it, just fill in the default charset set.
I've only noticed this since I switched to 2.0.7.610-devel. 2.0.7.609 was fine for me.
I was having this exact same problem. Whenever I tried to apply certain fonts, the text would revert to Arial. After updating the charset setting from <blank> to ANSI, the problem was solved. Don't know if that helps.
Using 2.0.7.619-devel
Ok, found the charset bug and fixed it. Most likely the reason that people were seeing Arial is that it's Windows' default fallback font. Next release will fix this properly.
You must log in to post.