Ah, missed the whole "user" part. If you use a Snow Leo+ help bundle and increment its version for each update, perhaps Help Viewer is smart enough to recognise the update?
On 14 Dec 2011, at 02:51, Graham Cox wrote: > Thanks, but that's even worse to ask the user to do on every update. > > I'm looking either for a) some way of indicating to the help system that it > needs to update the cached copy of our help or b) a way to force it to do so > using some API. > > I'm following up a hint I received offline - looks like our help bundle is > incomplete at the moment which could be part of the problem. > > --Graham > > > > On 14/12/2011, at 1:44 PM, Gleb Dolgich wrote: > >> This works for me: >> >> killall helpd >> rm -rf ~/Library/Caches/com.apple.help* >> >> -- >> Gleb Dolgich >> PixelEspresso >> http://www.pixelespressoapps.com >> >> On 13 Dec 2011, at 22:17, Graham Cox wrote: >> >>> With each update of our app, we typically change the help book. We're >>> finding that the system is very poor at recognising this and caches old >>> versions of the help which causes new stuff we add to be unavailable. While >>> I can manually trash the help caches and force an update, this isn't >>> something we can ask or expect of our users. >>> >>> Is there a supported way of forcing the help system to update or to discard >>> its caches? >> > _______________________________________________ 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
