font selection doesn't work [Archive] - Quintessential Forum

PDA

View Full Version : font selection doesn't work


harumscarum
05-05-2007, 07:40 AM
this i noticed since 116 version - i choose tahoma font than make it default and apply it to skin but after restarting qmp i see ugly arial font again without any chance to change it.
is there any way to make tahoma font permanent by font selection?


before restart

http://harum.scarum.net/tmp/01.gif


after restart

http://harum.scarum.net/tmp/02.gif

Todd The Kiwi
05-05-2007, 09:32 PM
bug 1744 (http://quinnware.com/forum/bugtracker.php?do=viewbug&bugtracker_bugid=1744) - not a bug.

harumscarum
05-05-2007, 09:50 PM
so what do you mean - no way to use another font in QMP after restart? only Arial?

fatal error
05-05-2007, 10:27 PM
crack open the skin and specify the fonts it uses. if you can't.....tell me which skin it is and i'll customize it for you.

Toe
05-05-2007, 11:28 PM
See that little "Set current as default" button? That's what you're looking for. :)

harumscarum
05-06-2007, 09:23 AM
See that little "Set current as default" button? That's what you're looking for. :)

i've told in my first post that i choose Tahoma font and than press both "Set current as default" buttons!
but still after restart of QMP i see Arial font even if Tahoma as "default font" and "for this skin only" is active. see screenshots which i posted "before restart" and "after restart"

harumscarum
05-06-2007, 09:25 AM
crack open the skin and specify the fonts it uses. if you can't.....tell me which skin it is and i'll customize it for you.

hi! i use Q-WAMP by loquito. i would be very grateful if you manage to set tahoma font permanently in that skin

Toe
05-06-2007, 10:31 AM
Hum, pretty sure I'd tried that in a previous ver and it worked...

fatal error
05-06-2007, 12:22 PM
done.....
PM me an email address to send it to.

fatal error
05-07-2007, 12:07 AM
nevermind, i'll attach it here

Tomy
05-09-2007, 10:10 AM
Hum, pretty sure I'd tried that in a previous ver and it worked...

I had the same problem with the previous build. Haven't tried it in this build.