Re: Issues with implementing WYWIWYG font menu
Re: Issues with implementing WYWIWYG font menu
- Subject: Re: Issues with implementing WYWIWYG font menu
- From: Graham Cox <email@hidden>
- Date: Wed, 06 May 2015 09:36:49 +1000
> On 6 May 2015, at 7:21 am, David Durkee <email@hidden> wrote:
>
> (the fonts I’m guessing)?
>
Why guess when you can measure?
However it is almost certainly the fonts. No matter how you end up displaying them, you still need to initialize them at some point. You can probably warm up the Font Manager by iterating through all of its fonts (maybe as a background task) but bear in mind that could occupy a lot of memory - which might not matter.
Back in the old days (pre Mac OSX) one of the frequently seen solutions to the Font menu problem was to save the font menu titles as images and use a custom menu definition to display these, loading the real font lazily when the user actually chose it. You can still do much the same trick these days I expect, using a custom menu item. It’s a lot of work just to avoid a small delay though.
—Graham
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden