You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When you add additional hotfolders,the perceived behavior is as if it is cloning the plugin with current settings included (which includes whatever notebook and directory the user had specified there in the base plugin's options).
whether that's a bug or a feature, it has the effect of duplicating all of those imports, presumably because it does not wait for the new hotfolder to be configured before executing its import actions.
propsals:
have a single hotfolder plugin options window.
spawn pairs of additional input fields for additional directories and corresponding notebook.
eliminate default auto import to all-notes section and any associated functionality entirely.
only execute hotloading when both the directory and its corresponding notebook field are populated.
if user specifies an invalid path, inform them and do not commit the change upon apply - the same goes for the corresponding notebook field.
If these values were valid during creation but become invalid later, show indicator inside the hotfolder options page instead of constantly throwing an error.
The text was updated successfully, but these errors were encountered:
After creating another hotfolder, Joplin must be restarted so that this hotfolder appears in the menu.
Dynamic changes in the plugin settings are not possible with the Joplin API, so a restart is necessary.
And no, the path for the hotfolder is not cloned and the other values have the default ones.
When you add additional hotfolders,the perceived behavior is as if it is cloning the plugin with current settings included (which includes whatever notebook and directory the user had specified there in the base plugin's options).
whether that's a bug or a feature, it has the effect of duplicating all of those imports, presumably because it does not wait for the new hotfolder to be configured before executing its import actions.
propsals:
The text was updated successfully, but these errors were encountered: