Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Image caching #222

Closed
gotschmarcel opened this issue Dec 2, 2014 · 11 comments
Closed

Image caching #222

gotschmarcel opened this issue Dec 2, 2014 · 11 comments
Labels
Milestone

Comments

@gotschmarcel
Copy link

Sometimes when an image has changed it is really annoying that MacDown has no button for reloading cached images.

@uranusjr
Copy link
Member

uranusjr commented Dec 2, 2014

There is a “Render” item in the menu. It does not really clear caches (only updates the HTML), but still works for me most often than not because MacDown does not really make use of the WebView’s caching mechanism. Maybe you can try that first?

@gotschmarcel
Copy link
Author

I already tried that, but still no effect. I had to rename the file and include that instead, to get it updated.

@uranusjr uranusjr added the bug label Dec 5, 2014
@uranusjr uranusjr added this to the 0.5 milestone Dec 5, 2014
@georgecrawford
Copy link

I've been annoyed by this as well. I can understand a latency updating remote images, but for local files referenced with relative paths, it would be great if a change to the last-modified date could trigger a reload.

@jkoelling
Copy link

I'd also be very happy if this gets changed. Sometimes the caching persists even over restarts of the application. This changed my workflow so much hat I actually started to double check my images all the time. (btw: I tried re-rendering, it didn't help. Only save way to get the updated image is renaming to a previously unused file name.)

@mmzoo
Copy link

mmzoo commented Mar 30, 2015

As a workaround, I add ?some=thing ?some=thing2 and ?some=thing3 etc. whenever I need to reload the image. That's at least faster than restarting the application.

@jkoelling
Copy link

Thanks for the workaround @mmzoo. Works like a charm and is much less annoying than renaming the files or restarting the application.

@LandonSchropp
Copy link

It would be nice if this issue were reopened. Adding a query parameter to the file name isn't intuitive.

@csinva
Copy link

csinva commented Jan 26, 2016

Fixing this issue would be amazing!

@uranusjr
Copy link
Member

uranusjr commented Nov 4, 2016

Wait no, this is a different issue. Sorry.

@uranusjr uranusjr reopened this Nov 4, 2016
@uranusjr
Copy link
Member

uranusjr commented Feb 6, 2017

Fixed in #747. 🎈🎈🎈

@uranusjr uranusjr closed this as completed Feb 6, 2017
@working-name
Copy link

Issue still present in 0.7.1 (870) on 10.12.6 unfortunately. Maybe that private API got renamed or something?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

8 participants