Thanks for your input Mark,

I would agree that properly installing the font is the best approach. But as I can't seem to get my question answered by Apple about requirements for the Mac app store, I'm assuming that they won't allow it.

I did some tests quite a while ago with revFontLoad and found that once in a while my stack loaded faster than revFontLoad could load the font. This happened when you booted the program by double-clicking one of the user stacks. I know I could tell people to always start the app, then open the user stacks, but invariably someone would do otherwise. As I recall, though, I was loading the font on preOpenStack of my main stack. I will try it with Startup and maybe that will help.

Marty
Hi Marty,

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.

--
Best regards,

Mark Schonewille


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

Reply via email to