>
>In addition, I now find that I cannot set the font of the fields
>manually to any font on my Windows 98 machine. No matter what I choose,
>the font becomes tiny, unreadable, sans-serif something displayed at
>about 8 point with wacky word wrap and half inch gaps between words
>where the spaces are.
>
>There is no "Times" font on my Windows machine, but if set it to "Times"
>manually in the message box, it displays just like on the Mac and looks
>fine (only it doesn't on the client's machines.) If I set it to "Times
>Roman" from the font menu it goes screwy with the tiny sans-serif font.
>
>Looks like something corrupted to me.

Hello,
I can only offer a meager consolation: the fonts have actually been 
my worst and most time-consuming problem ever since I started using 
MC on both Mac and PC. My experiences so far: I just use "Geneva" on 
Mac and "Arial" and "MS Sans Serif" on PC.

"Helvetica" which MC recommends, is not available as standard font on 
PC (I may be wrong, but that's what I have seen so far). I have also 
experienced problems with resetting the fonts when converting a stack 
from SuperCard in which the textfont used was Helvetica.

One thing which I wish MC would do something about is the way Font 
Chooser acts. The very first time you use it it behaves as it should. 
The next times very often you change a font or another attribute 
there and nothing happens.

Or when you ask in the msg: "put the textfont of fld ..." it says one 
thing, if you ask "put the textfont of char 1 to -1 of fld ..." it 
says another. Only the last one gives the correct answer in some 
cases.

The problems arise since I often use various attributes for the same 
field on the two platforms. Sometimes one word is highlighted by 
using bold, or set in another colour. So what I do now (of which I 
have no guarantee of the consistency): If the text is permanent I set 
the font attributes of the field for the platforms in 
preOpenCard-handlers.

The real problems start when new text is put into the same field. I 
have not been able to test out all the variants of MC behaviour when 
I empty the field, or "set the textfont of fld ... to empty" (as 
Monte Goulding also suggested) before putting the new test into the 
field.

The scripts I use may be like this one:
   if the platform = "macos" then
     set the textfont of fld "setn" of cd "oevkort" to geneva
     set the textsize of fld "setn"  of cd "oevkort" to 16
     set the textstyle of fld "setn"  of cd "oevkort" to bold
     set the textheight of fld "setn"  of cd "oevkort" to 22
   end if
   if the platform = "win32" then
     set the textfont of fld "setn" of cd "oevkort" to arial
     set the textsize of fld "setn"  of cd "oevkort" to 18
     set the textstyle of fld "setn"  of cd "oevkort" to plain
     set the textheight of fld "setn"  of cd "oevkort" to 20
   end if

But very often it seems to be necessary to add  "...of char 1 to -1 
of fld..." (not for the textheight, but for the others). Specifying 
the chars does not work with buttons, only with fields.

Sometimes I wonder if it would be better to maintain separate 
versions for the platforms, but having just one version has been my 
choice so far.
 

-----------------------------------------------------------
1. amanuensis Signe Marie Sanne      e-mail: [EMAIL PROTECTED]
Romansk Institutt                            tel:  +47 55 58 21 27
Oysteins gt. 1
5007 Bergen          http://www.hf.uib.no/hfolk/mlab/default.html
Norway
-----------------------------------------------------------

Archives: http://www.mail-archive.com/[email protected]/
Info: http://www.xworlds.com/metacard/mailinglist.htm
Please send bug reports to <[EMAIL PROTECTED]>, not this list.

Reply via email to