I'm trying to set a trigger so when I save my kdbx in my documents (desktop) it will sync with the copy in my dropbox.
The event is "saving database file" ; equals(file path on desktop)
The action is "synchronize active database with a file/url" ; (path of file in dropbox)
I don't understand why it goes infinite loop, I have the local kdbx open and the other closed.
I would think since I specified path's, this would not happen?
Thanks in advance for your help!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
patheticpat - thanks for the workaround. It resolved this problem for me. Can you explain how/why this approach resolves the problem. It appears the first step is to disable the trigger so I'm curious how the trigger is still executing given this is the first step??
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
When you use a triggered event to disable the trigger, the event will run to completion. This allows you to disable and then re-enable the trigger system.
cheers, Paul
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm trying to set a trigger so when I save my kdbx in my documents (desktop) it will sync with the copy in my dropbox.
The event is "saving database file" ; equals(file path on desktop)
The action is "synchronize active database with a file/url" ; (path of file in dropbox)
I don't understand why it goes infinite loop, I have the local kdbx open and the other closed.
I would think since I specified path's, this would not happen?
Thanks in advance for your help!
Maybe sync = saving?
Try SAVED database file.
cheers, Paul
I was running into the exact same problem and was able to work around it by defining 3 actions for that particular trigger:
"Change trigger on/off state": switch current trigger to off
"Synchronize active database with a file/url": perform the actual synchronization
"Change trigger on/off state": switch current trigger back on
Hope this helps,
Michael
patheticpat - thanks for the workaround. It resolved this problem for me. Can you explain how/why this approach resolves the problem. It appears the first step is to disable the trigger so I'm curious how the trigger is still executing given this is the first step??
When you use a triggered event to disable the trigger, the event will run to completion. This allows you to disable and then re-enable the trigger system.
cheers, Paul