bhugh

FYI I put together a little utility to trim, prune down, and split .tcx files, as you're discussing. https://github.com/bhugh/tcxprune I tried this Prune GPS Tool, GPSBabel a few different ways, and a bunch of other alternatives that looked like they would work. But none of them quite did the job with .tcx files, so I made this little single-use utility that does the job. It runs under Windows, any Unix environment, macOS, even Android, and as an online run-in-a-web-page utility at Repl.it.

#1 It's the same except you assume the DropBox folder already exists. Yes, which will be the case for 99.9% of users. They are choosing to use the Dropbox syncronization method precisely because they already have Dropbox installed. For the those without Dropbox, it would be sensible for them to install Dropbox first as well, and then their folder will be in a different location than the instructions specify as well, and they will not be able to make heads or tails of the instruction "24. Set Dropbox...

Jumping in a bit late I know, and steelej already covered the essentials . . . but in a little mroe detail: As I understand it, this recommended scheme with the triggers does indeed solve exactly the problem you are trying to solve. if you synchronize (save) the database at the exact same time dropbox will synchronize only one of the databases and will create a conflict copy on Dropbox, regardless of whether you edited the same key or different ones. That is true. However, what you are missing is...

Thank you - I've update the post above with your suggestions and some more edits for clarity and consistency. steelej and anyone else, please let me know if you see anything else that can be clarified or corrected in this updated version: https://sourceforge.net/p/keepass/discussion/329221/thread/99814bd100/#f1ce

As I mentioned in the previous post, maybe just a quick edit of the current instructions would help clarify what I'm talking about. As I say, it's 98% there. Just a few word-changes here and there are all that is really needed. The instructions below assume that you have created KeePass database and saved it somewhere on your hard drive (outside of Dropbox). We call this the KeePass Local Copy. The instructions below also assume that you have Dropbox installed and running, with your local Dropbox...

As I mentioned in the previous post, maybe just a quick edit of the current instructions would help clarify what I'm talking about. As I say, it's 98% there. Just a few word-changes here and there are all that is really needed. The instructions below assume that you have created KeePass database and saved it somewhere on your hard drive (outside of Dropbox). We call this the KeePass Local Copy. The instructions below also assume that you have Dropbox installed and running, with your local Dropbox...

As I mentioned in the previous post, maybe just a quick edit of the current instructions would help clarify what I'm talking about. As I say, it's 98% there. Just a few word-changes here and there are all that is really needed. The instructions below assume that you have created KeePass database and saved it somewhere on your hard drive (outside of Dropbox). We call this the KeePass Local Copy. The instructions below also assume that you have Dropbox installed and running, with your local Dropbox...

As I mentioned in the previous post, maybe just a quick edit of the current instructions would help clarify what I'm talking about. As I say, it's 98% there. Just a few word-changes here and there are all that is really needed. The instructions below assume that you have created KeePass database and saved it somewhere on your hard drive (outside of Dropbox). We call this the KeePass Local Copy. The instructions below also assume that you have Dropbox installed and running, with your local Dropbox...