Feature request: History/Log file/viewer
Posted: Sun Oct 26, 2014 12:36 pm
Hello all,
Curious to hear whether anyone else might find something like the suggested useful? Alternatively - is something like the requested already possible?
With the usual caveat of my not knowing nearly enough about programming, to gauge in any shape or form whether this is something "simple", I wonder if it would be possible to introduce a basic "log-file" of recent actions that have taken place in Bookends.
I realised today, purely through my own fault, that I accidentally deleted several citations/references, from my BE12 library. My 'bug' took the form of a KM macro, that suddenly no-longer works as it should. Where it was supposed to delete the entry in the search field, it skipped a step or two (timing problems), and instead deleted the reference selected in the library [the macro ended with a "return" command], which selected the pop-up menu warning, saying this cannot be undone. So literally in the blink of an eye, I [presumably] deleted a few, before I realised what was happening...
AFAIK, there is no way to check which files were so deleted? Could this be something that would be tracked by some sort of a "history/log" viewer, that runs in the background, 'recording' all recent file actions inside the library, including those silly/accidental deletes?
Curious to hear whether anyone else might find something like the suggested useful? Alternatively - is something like the requested already possible?
With the usual caveat of my not knowing nearly enough about programming, to gauge in any shape or form whether this is something "simple", I wonder if it would be possible to introduce a basic "log-file" of recent actions that have taken place in Bookends.
I realised today, purely through my own fault, that I accidentally deleted several citations/references, from my BE12 library. My 'bug' took the form of a KM macro, that suddenly no-longer works as it should. Where it was supposed to delete the entry in the search field, it skipped a step or two (timing problems), and instead deleted the reference selected in the library [the macro ended with a "return" command], which selected the pop-up menu warning, saying this cannot be undone. So literally in the blink of an eye, I [presumably] deleted a few, before I realised what was happening...
AFAIK, there is no way to check which files were so deleted? Could this be something that would be tracked by some sort of a "history/log" viewer, that runs in the background, 'recording' all recent file actions inside the library, including those silly/accidental deletes?