Setting fonts

Charles Hartman charles.hartman at conncoll.edu
Thu Jul 7 10:12:45 EDT 2005


On Jul 7, 2005, at 9:52 AM, Ken Ray wrote:

>
>
>> I need to modify what I wrote before, quoted below.
>>
>> The text after the special-font (Courier) lines _does_ get set to
>> whatever the new default or owner's font is -- UNLESS it (the lines
>> without a specified contains any text _style_ changes. A bit in bold,
>> or marked as a link, interrupts the transformation, and any text
>> after that is in the old, pre-change default font.
>>
>
> That's correct. Inheritance of text attributes is broken as soon as  
> any
> style changes. I wish it weren't so, but this is indeed the case.

Oh dear.

>
>
>> How should I get around this? I can imagine searching each card,
>> putting any special-format text into temporary variables, setting the
>> style of everything to Plain, changing the font, then
>> reformatting . . . a nightmare. At the moment, nothing better is
>> occurring to me.
>>
>
> I have successfully used a frontScript that would trap preOpenCard  
> and then
> repeat through all of the fields and set their text attributes to a  
> known
> common value, but also checking a custom property of the fields to  
> see if
> special handling should occur for a particular field. It works  
> really fast,
> and isn't too many lines of code.
>

Cool. But (1) what about "special handling" that affects not a whole  
field but some chunks within the field? And (2) doesn't this approach  
take an awful lot of (that is, potentially a noticeable amount of) time?

Charles Hartman



>
>
>
>
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your  
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-revolution
>

Charles Hartman
Professor of English, Poet in Residence
Connecticut College
charles.hartman at conncoll.edu
*the Scandroid* is at cherry.conncoll.edu/cohar/Programs








More information about the use-livecode mailing list