my Scrivener project is in my Dropbox along with my related Aeon Timeline file, right.
i’m working on my iMac and on my MBA. I NEVER open either my Scrivener project or my Aeon Timeline at the same time on both computers.
Problem is with syncing.
i can sync my Aeon Timeline with my Scrivener project on one computer only since i use a different user name on each computer. I’d like to be able to sync on both computers.
in other words, when trying to sync (from within Aeon Timeline, which seems to be the only way according to the developer) on the second computer, my Scrivener project is regarded as not valid for syncing.
is there a workaround?
what about (although i’m not sure it’ll help) creating a symbolic link for “Application Support > Scrivener” from my Dropbox folder to both computers?
note: for the time being, both “Application Support > Scrivener” and “Application Support > Aeon Timeline” do NOT seat in my Dropbox but in each computer in “/user/library/application support”.
I am the developer of Aeon Timeline.
I am currently in the process of creating version 1.1 and am working on the Scrivener syncing functionality at the moment.
If you can email details of how your computers are setup - directory structure etc - to firstname.lastname@example.org, I will see if I can modify Aeon to work in ths scenario - perhaps using a relative path in addition to an absolute path, or using some other means to protect against syncing with different Scriv projects without relying on the path at all.
I hadn’t considered DropBox for the current implementation, but hopefully I will be able to design for t in the next update.
thanks for your reply
i’m therefore sending you an email with the requested details.
As requested on your previous post, I sent you my project on December 10th, 2012 but I haven’t heard from you so far.
I’m therefore totally unable to sync my Aeon Timeline on more than one computer. I hope my MBA doesn’t need to go to repair and that i can still use it for syncing…
I’m not sure I received your previous email, could you possibly send it again?
I am on the verge of releasing the 1.1 beta to some limited testers, so I can attempt to fix up this problem before that and let you test out the beta also.
Just to update, sorry, I have found your email.
I will take a look at the issue today and see if I can develop an easy fix for it.