m.schonewille at economy-x-talk.com
Sat Jan 22 19:35:46 EST 2011
Mac OS X 10.5 and later might detect the usage of your font, before your script gets a chance to load that font. If that happens, the user will see a system dialog window, asking whether to allow your application to use that font. This might also happen, if your application writes the font from a custom property to the temporary folder and subsequently crashes.
The best approach is to install the font properly and to include a copyright statement and license conditions specific to the font in the license conditions of your application. (I can't resist the opportunity to say that the Installer Maker Plugin includes a feature to install fonts).
If you really don't want to do that, you might try to use the splash stack approach and write the font to disk and load it into memory before opening any stacks that use the font.
Economy-x-Talk Consulting and Software Engineering
New: Download the Installer Maker Plugin 1.5 for LiveCode here http://qurl.tk/ce
On 22 jan 2011, at 21:49, Marty Knapp wrote:
> I want to package a font with my Mac only app and use revFontLoad to load it into memory. Is there a problem with just tucking it inside the application bundle and loading it from there? Or should I put it into a custom property and then write it out to the user's hard drive and put it into use from there?
> My preliminary tests show that it works from inside the bundle. I'm just wondering if there's something that I'm not aware of that would make this a bad idea.
> Marty Knapp
More information about the Use-livecode