Hi Steve,
Sorry to keep bugging you, but I've got one more question. I was trying to create a new job earlier where the base directory of the source didn't already exist on the destination, and I could not get it to work - everytime it ran, it failed to make the directory.
Example:
source:
C:\workbench\mydir
destination:
- does NOT already have either a \workbench or \workbench\mydir directory
Running a copy, mirror or equalize failed to create the destination directory. I know that I could just manually copy the directory from source->destination first, but that would kind of defeat the purpose of the application 
Actually - I was thinking that if I ended up creating a lot of these jobs, and then ran them (for example) from the flash drive to a PC that didn't have any of the directories that I might not even realize that there was a failure if I didn't pay close enough attention - especially if I'm running a LOT of jobs at once.
thanks again, Steve!
Edited to add: This issue is independent of the app version.
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on Facebook
Follow us on LinkedIn
Follow us on Twitter
Follow us on Mastodon
Follow us on BlueSky
That isn't the point of the app. The point is to work on two EXISTING directories. It'll create the necessary directories inside of it. But it doesn't create the destination directory itself (nor should it in my opinion since if it doesn't already exist, the user probably entered it wrong).
Sometimes, the impossible can become possible, if you're awesome!
I think that I'll have to disagree with you, John. The application also includes backup functions - and the destination directory is not needed for those instances. I can think of many situations where this program would be extremely useful where the destination directory didn't already exist. Somewhere between a mirror and a (compressed) backup. Well, basically an uncompressed backup - if I'm bouncing between multiple PC's with a flash drive with many jobs on it I don't want to have to look at each job and figure out if the destination directory exists first - I want the app to be smart enough to realize to create that destination directory first. Perhaps even just allow this as a user-configurable setting.
I played with the program here, and found that it will create ONE directory if it doesn't exist, but not two.
For instance, using your example of source:
C:\workbench\mydir
If c:\workbench exists, then Toucan can make c:\workbench\mydir
If c:\workbench does NOT exist, then Toucan can't make c:\workbench\mydir
I didn't try including another directory to sync under mydir, but you can play with that yourself.
Jim
neutron1132 (at) usa (dot) com
Actually, that makes a lot of sense. As an example, say you were syncing your music folder between these directories:
C:\Documents and Settings\MyLogin\Documents\Music
X:\Documents\Music
It would be reasonable to create the Music folder if it didn't exist since that is what you're syncing. I don't think it would be reasonable to create Documents and Settings, MyLogin, Documents and Music, though.
I very much like how Steve has this set right now since it would prevent going a long time having accidentally synced say drive D:\Documents... in the above scenario. It would be possible to include an advanced setting in jobs that allows for full path creation on sync, though, to fulfill the requested scenario for the parent, but I think it should *definitely* be off by default.
Sometimes, the impossible can become possible, if you're awesome!
I shall look at adding this in as an option, but it probably wont make it into the next version as I am trying to wrap it up, hopefully the version after though.
That would be great!
Hi Steve, just wanted to point out that the issue in my original post seems to be working just fine now in 2.0.2PR3.
Many thanks!
I didnt do anythnig to change this in PR3 so I can only guess that in fixing and changing other parts of the code this was changed, so I shall just leave it as is