EMULAB Forum

clrmamepro [English] => clrmame Discussion => Topic started by: Roman on 08 September 2011, 22:26

Title: font selection test build
Post by: Roman on 08 September 2011, 22:26

You suffer from the easter-europe utf8 tree control font issue?
You always wanted a larger font for the scanner output?
You got the circular zip rename issues?

Well, then get this test build here and unrar it over your installation:
http://mamedev.emulab.it/clrmamepro/binaries/cmpFont.rar (http://mamedev.emulab.it/clrmamepro/binaries/cmpFont.rar)

This build fixes circular rename issues and got a font selector. It will change the font for the scanner tree output and the set-information tree and list control.
You can find the font selector in the "View" context menu of the scanner (right click in the scanner tree window, select View, then Select Font at the bottom.
For the Easter Europe UTF8 issue you should select a font which supports all characters (most likely Arial or Segoe UI do...).

Enjoy testing....I will enjoy holidays....

Title: Re: font selection test build
Post by: oddi on 09 September 2011, 03:43

Roman u great!. Now correct view in Scanner window and setinfo window :)
Thanks a lot

Title: Re: font selection test build
Post by: Roman on 09 September 2011, 07:15

You're welcome...
Any place where you want to be able change the font? Theorectically all treecontrols are affected by the missing-character issue....so I might think of the profiler....
but I guess for now you're happy ;)

Title: Re: font selection test build
Post by: oddi on 09 September 2011, 07:41

For any place change fonts - np , if u wanna.  Btw - it's funny - Arial 24 Bold!, pfiyyyy..need new 24-26'' monitor :) hehehe.
U know something about  torrentzip - because when tzip archive , tzip broken utf8 characters.
Dont know where is problem ? me, clrmame or tzip. tnx

Title: Re: font selection test build
Post by: Roman on 09 September 2011, 11:46

It's torrentzip's fault. Torrentzip does not support utf8 stored names and kills the utf8 encoding since it most likely encodes the names again with local code page encoding.