Smalltalk › Cincom › VisualWorks

[vwnc] XFont problem

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

2 messages Options

grt

[vwnc] XFont problem

Hi all,

I have a problem related to XFont. My application is in VW 7.6 and is hosted on redhat.

It seems while connecting through a Nx server the VW required a font -adobe-courier-medium-r-normal--*-117-75-75-m-*-iso8859-1 (and some more similar to this with -* for pixelSize parameter) which the server admin solved by mapping it to a different available font on the font.alias file as below

-adobe-courier-medium-r-normal--*-117-75-75-m-*-iso8859-1

-adobe-courier-medium-r-normal--12-120-75-75-m-70-iso8859-1

The problem with application connected through Nx was that some Actionbutton labels were not visible.

This was done some 8 months back and this mapping solved the issue. But now when my application queries for a courier - 15 px font (in the application server itself and not thu Nx) which

is actually invalid and not installed it returns this -adobe-courier-medium-r-normal--*-117-75-75-m-*-iso8859-1 font (matchFont: requestedFont allowance: allowance)

and raises an Exception in generateFontNameFor: prototypeName using: newSize since it expects "0-" instead of the "*-".

My Doubts are

1) but even if i ask the wrong font the matchFont: should return me the font without -* in it so that it wont cause an exception later in createFont, am i correct?Like a 14 px one.

2) Has anyone come across this kind of issue before?if yes please let me know how you dealt with it.

Below is the stack.Here i am simply doing a Test as compsed text , having runs #(family->'courier' #pixelSize->15)

XFont class(Object)>>error:XFont class>>generateFontNameFor:using:XFont class>>createFont:toResemble:on:FontPolicy>>findFont:CompositionScanner>>setStopConditionsCompositionScanner>>endOfRunCompositionScanner>>comp...leftMargin:rightMargin:ComposedText>>nextLineItem:line:with:ComposedText>>composeAllComposedText>>compositio...th:text:style:fitWidth:ComposedText class>>withText:style:ComposedText class>>withText:Text(CharacterArray)>>asComposedText

I hope someone will be able to shed some light on to this.

Thanks in Advance,

G R Thushar

--
thuchu

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

Alan Knight-2

Re: [vwnc] XFont problem

I'm afraid I don't know enough about the specifics. But in general, VW is not going to require a font with that level of specificity. It's going to look for what fonts are available on the system and try to find one that seems sufficient to it. When we've seen problems like that, the root cause is often that when it asks for the list of fonts, it's given back a font which will then fail if it tries to use it. So one thing to check if there's an issue with the font configuration on the machine.

At 02:07 PM 2009-12-22, Thushar G R wrote:

Hi all,

I have a problem related to XFont. My application is in VW 7.6 and is hosted on redhat.

It seems while connecting through a Nx server the VW required a font -adobe-courier-medium-r-normal--*-117-75-75-m-*-iso8859-1 (and some more similar to this with -* for pixelSize parameter) which the server admin solved by mapping it to a different available font on the font.alias file as below

-adobe-courier-medium-r-normal--*-117-75-75-m-*-iso8859-1
-adobe-courier-medium-r-normal--12-120-75-75-m-70-iso8859-1

The problem with application connected through Nx was that some Actionbutton labels were not visible.

This was done some 8 months back and this mapping solved the issue. But now when my application queries for a courier - 15 px font (in the application server itself and not thu Nx) which
is actually invalid and not installed it returns this -adobe-courier-medium-r-normal--*-117-75-75-m-*-iso8859-1 font (matchFont: requestedFont allowance: allowance)
and raises an Exception in generateFontNameFor: prototypeName using: newSize since it expects "0-" instead of the "*-".

My Doubts are

1) but even if i ask the wrong font the matchFont: should return me the font without -* in it so that it wont cause an exception later in createFont, am i correct?Like a 14 px one.
2) Has anyone come across this kind of issue before?if yes please let me know how you dealt with it.

Below is the stack.Here i am simply doing a Test as compsed text , having runs #(family->'courier' #pixelSize->15)

XFont class(Object)>>error:XFont class>>generateFontNameFor:using:XFont class>>createFont:toResemble:on:FontPolicy>>findFont:CompositionScanner>>setStopConditionsCompositionScanner>>endOfRunCompositionScanner>>comp...leftMargin:rightMargin:ComposedText>>nextLineItem:line:with:ComposedText>>composeAllComposedText>>compositio...th:text:style:fitWidth:ComposedText class>>withText:style:ComposedText class>>withText:Text(CharacterArray)>>asComposedText

I hope someone will be able to shed some light on to this.

Thanks in Advance,

G R Thushar

--
thuchu
_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

Alan Knight [|], Engineering Manager, Cincom Smalltalk

[hidden email]

http://www.cincom.com/smalltalk

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc