save button doesn't work about qlmarkdown HOT 11 CLOSED

@hazarek thats not fair. The app is still very early stage. If you don't like how it works propose a PR to fix it. But don't badmouth the time and effort someone puts into this in their free time.

from qlmarkdown.

@hazarek thats not fair. The app is still very early stage. If you don't like how it works propose a PR to fix it. But don't badmouth the time and effort someone puts into this in their free time.

You are right sorry. I'm just so excited. @sbarex sorry. Thanks for the plugin.

from qlmarkdown.

The extension inline local images is on?

from qlmarkdown.

Yes, I found the problem. When I relaunch finder, the permission dialog appeared and was fixed. the save button does not work. After restarting finder, the settings are applied.

from qlmarkdown.

MacOS handle the preferences with a cache system.
Perhaps by restarting the Finder they had not had time to save themselves?

from qlmarkdown.

MacOS handle the preferences with a cache system.
Perhaps by restarting the Finder they had not had time to save themselves?

I don't know. Also, there is currently no way to know if the settings are saved or applied. (Nothing happens when the save button is clicked.)

from qlmarkdown.

When you make a change on the settings, the red close window button show the dirty status. if the save is successful the dirty status will be reset.

from qlmarkdown.

When you make a change on the settings, the red close window button show the dirty status. if the save is successful the dirty status will be reset.

this is top secret. You should put a label that says "saved. or it can be a flash effect like TextEdit"

from qlmarkdown.

Also save menu always disabled

from qlmarkdown.

ahah, yes it's not very intuitive.
The menu action is not linked to the action of the button... new release will fix it.

from qlmarkdown.

The changes are reflected even without a Finder restart but it takes more time. It was nearly one minute on my machine at one point. But like @sbarex said some caching issues. Maybe there is a way to tell macOS to force prune the cache?

from qlmarkdown.