On 2. Sep 2020, at 02:40, Carl Hoefs via Cocoa-dev <cocoa-dev@lists.apple.com> wrote: > I've tried setting UIImageView.image=nil, UIImageView.animationImages=nil, > toggling UIImageView.hidden, wiping the sandbox, etc., but no joy. Of course, > restarting the app does force-flush the cache, but that's a no-go. > > The only way I've found to invalidate UIImageView's caching (without killing > the app) is to play games like generating unique filenames for each run of > the processing loop of the app. Apparently UIImageView tracks _filenames_ to > determine when to flush/update its cache! > > So, if there actually exists a kosher way to do this, I welcome any/all hints!
I don't have a good answer, but I think this may be more that UIImage caches the images, not UIImageView. Maybe you can find something in UIImage's docs/headers? Cheers, -- Uli Kusterer "The Witnesses of TeachText are everywhere..." http://www.zathras.de _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
