cacheTechNote

Custom Table

Accessorizer’s “Custom Table” allows you to cache your properties in memory or to disk.

IMPORTANT: Tech Note on Custom Table Cache

It's critical to note that the caching scheme is uniqued on ivar name only.

This means if you use a single cache across multiple classes or across an entire project,

you are bound to have name clashes. Please watch the video to the right for a tutorial.

The solution:

A) if you need a cache persisted to disk, then create a cache specific to that class/file and name it accordingly. This requires file management on the part of the developer.

B)if you just need to make some changes in the custom table and are going run a few generations as in cmd-1, cmd-2, cmd-4 etc and you don't want your custom changes to get blown away, then just use the default cache and clear the cache if you move to another class, let Accessorizer make a new cache in memory as you make custom changes in the custom table. This scenario is useful on a per session basis or if you are working on one class for any length of time.

*** NOTE: as a convenience, upon quitting, unless you’ve saved your cache to a specified file path, Accessorizer will save the current cache in memory out to ~/Library/Application Support/Accessorizer/AccessorizerCachedProperties provided the “use cache” switch is turned ON. When you next launch Accessorizer, and if the “use cache” switch is ON, the file will load the cache from disk into memory. If you wish/need, you can clear the cache in the custom table panel.