Saved changes are applied with a delay. about qlmarkdown HOT 6 CLOSED

The host application and the extension share preferences, however the extension loads them at startup and no longer updates them until your process is terminated. So if you keep the ql markdown preview open or if you continue to view other .md files in quick succession the extension is not released and therefore the preferences are not updated.

I don't know if it is appropriate to force the loading of preferences every time a file is read (with a performance penalty) or to keep things like this.

from qlmarkdown.

this is not an important issue, Live update is required while creating theme (while writing css). The changes I made in "custom.css" appear instantly with the refresh button.

from qlmarkdown.

Yes, because the css file is reload every time.

from qlmarkdown.

I don't know if it is appropriate to force the loading of preferences every time a file is read

You could also place an empty file in the shared group directory. And only check whether the file exists on every parse. If the file exists, reload the preferences and delete the temporary file.
(Unless there is a way to directly communicate with the extension. Idk. e.g. the network extension has an API to send data from the host app to the extension. Maybe there is a similar method for QL extensions?)

from qlmarkdown.

In next release I use a message notification to force the settings refresh.

from qlmarkdown.

Fixed in 1.0b7.

from qlmarkdown.