On Mar 2, 2015, at 15:13:01, Mike Abdullah wrote:
>
> Or you can bump up the -imageVersion
Ah, cool. Thanks! That allows me to stick with shorter imageUIDs.
--
Steve Mills
Drummer, Mac geek
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Ple
Or you can bump up the -imageVersion
> On 2 Mar 2015, at 21:54, Steve Mills wrote:
>
> On Mar 2, 2015, at 14:23:03, Dave Fernandes
> wrote:
>>
>> Your IKImageBrowserItem must change its returned imageUID when the
>> imageRepresentation changes so that the IKImageBrowserView knows to recache
Oops, yes imageVersion is what you should use. It’s been a long time since I
looked at this code (Leopard, I think).
> On Mar 2, 2015, at 4:13 PM, Mike Abdullah wrote:
>
> Or you can bump up the -imageVersion
>
>> On 2 Mar 2015, at 21:54, Steve Mills wrote:
>>
>> On Mar 2, 2015, at 14:23:03,
On Mar 2, 2015, at 14:23:03, Dave Fernandes wrote:
>
> Your IKImageBrowserItem must change its returned imageUID when the
> imageRepresentation changes so that the IKImageBrowserView knows to recache
> the image.
Ah. I was using a shorter string because using the full path seemed wasteful
and
Your IKImageBrowserItem must change its returned imageUID when the
imageRepresentation changes so that the IKImageBrowserView knows to recache the
image.
Dave
> On Mar 2, 2015, at 12:37 PM, Steve Mills wrote:
>
> Is there any way to force IKImageBrowserView to throw out a cached thumbnail
>
Is there any way to force IKImageBrowserView to throw out a cached thumbnail
and regenerate it on a changed imageRepresentation? I can definitely see that
imageRepresentation is returning a different url, but the browser still draws
the old one, even after calling reloadData.
--
Steve Mills
Dru
