Philosophical questions about the fontNames

Bob Sneidar bobsneidar at
Thu Mar 12 13:45:40 EDT 2020

Another approach might be to find a font or subset of fonts that looks the same on all platforms and use that. You may have to pay for the font(s) but you gain consistency. 

Bob S

> On Mar 12, 2020, at 10:23 , Paul Dupuis via use-livecode <use-livecode at> wrote:
> Yes, it does. Lacking a detailed technical understanding of the ridiculous complexity of the macOS (or Windows for that matter), is one reason we used/use HyperCard, SuperCard, MetaCard, Revolution, LiveCode for the past 25+ years for our app development.
> It *SEEMED* like a reasonable attempt at HIG compliance to set the fonts of our objects to the special names and also *SEEMED* like it was then reasonable to want to show what font was selected in a menu, but it is absolutely true that I was assuming that "(Text) became Segui UI on Windows and Calibri (or whatever) on macOS and NOT something like .AppleSystemUIFont!
> So, we'll revert our code back to the classic conditional of:
> switch platform()
>    case "Win32"
>       set the textFont of fld "X" to "Segue UI" -- or whatever seems appropriate
>       set the textFont of fld "Y" to "Segue UI"
>       ... set all the rest of the objects
>       break
>    case "MacOS"
>      set the textFont of fld "X" to "something"
>      ....
>      break
>    case "next platform"
> etc.
> We went down a rabbit hole where, without knowing better, it seemed that the above could be replaced with
> set the textFont of fld "X" to "(Text)"
> set the textFont of fld "Y" to "(Text)"
> etc
> and eliminate the switch statement entirely.

More information about the use-livecode mailing list