|
Rivo Newbie
Joined: 11 Apr 2006 Posts: 9
|
Posted: Sat Aug 09, 2008 9:07 pm
[2.35] Display problems--Transparent gaps after changing Font |
Sorry if this has been mentioned.
The session windows of Cmud display the text well if the Font(Style) remains default(i.e. Courier8).
But if I change the Font to some other, say Dotum8, the text becomes narrower and shorter and consequently
leaves blanks to the ends and gaps between the lines. Unfortunately these gaps and blanks do not have the
background color but are trasparent, showing whatever behind the Cmud window, like wall-paper, IE, chatting
window, etc. That's very annoying when viewing/reading the Cmud session window.
Can any one solve this problem buy changing the Cmud settings?
Cheers |
|
|
|
Seb Wizard
Joined: 14 Aug 2004 Posts: 1269
|
Posted: Mon Aug 11, 2008 9:58 pm |
Is the problem fixed by (a) minimizing and restoring the CMUD window; (b) closing and reopening your session; (c) closing and reopening CMUD?
What version of Windows are you using? |
|
|
|
Zugg MASTER
Joined: 25 Sep 2000 Posts: 23379 Location: Colorado, USA
|
Posted: Tue Aug 12, 2008 4:42 pm |
I was able to reproduce this problem and have added it to the bug list. Not sure if it's just related to a problem with the Dotum font since it doesn't seem to happen with other fonts.
|
|
|
|
Rivo Newbie
Joined: 11 Apr 2006 Posts: 9
|
Posted: Fri Aug 15, 2008 8:33 pm |
Hello guys, thanks for replying.
It actually happens whenever the new font can introduce blanks/gaps.
Many fonts with small size (like 8) will leave a blank area to the end of each line. These blanks can be filled by increasing the font size.
Some fonts (e.g. 'Batang', 'Times New Roman') will introduce gaps between text lines which cannot be eliminated by changing font size.
This problem cannot be solved by either a), b) or c) that Seb has mentioned.
I am using WindowsXP SP2.
Sorry I don't have time to try all the fonts available.
Cheers |
|
|
|
Zugg MASTER
Joined: 25 Sep 2000 Posts: 23379 Location: Colorado, USA
|
Posted: Sat Aug 16, 2008 12:20 am |
Btw, this is fixed in the 2.36 version already.
|
|
|
|
|
|