I have an application with a custom UI which uses vector-based PDFs
for all images.
I'm now seeing what appears to be an image loading problem. I
believe I first saw this a couple of years back, but it would only
occur rarely when running the application via the debugger. Now,
I'm able to reproduce it about 20% of the time when running the
demo flavor of the app from Finder.
But, only a single image is not being loaded properly. And, such
image happens to always be the very first image that is loaded by
the app. The image was created with Illustrator and is a simple
rounded-rectangle filled with a gradient. The background is
transparent. When it doesn't load correctly, the entire bounds of
the image is filled by the gradient. It's as if the 'clipping
path' of the gradient is not being applied.
If I edit my main nib's first loaded button to point to a different
image, that image will sometimes fail. Thus, I know it's not an
issue with the PDF images themselves.
Has anyone else seen any issues like this with PDFs being loaded
into NSImage instances?
As a workaround, I'm going to create a dummy image (duplicate of
the PDF in question; just renamed) that I'll load at app startup.
Perhaps there is some PDF functionality that isn't always being
initialized?
I'm going to also post this to quartz-dev, so may continue the
thread there.
Even stranger still...
The demo app that sometimes fails is installed in the boot volume's /
Application/Instant Interactive<TM> Drills Demo/ folder where <TM> is
actually the little trademark symbol (option-2 under MacRoman).
If I rename that folder (e.g. prefix it with '_', append a '1'), I
cannot get it to fail. The only thing that would do is of course
alter the full path of the image that is ultimately loaded. Is this
some cache file that has gone bad somewhere?
