ERROR 32 WHEN TRYING TO SET FILE TIME HOW TO
ERROR 32 WHEN TRYING TO SET FILE TIME FOR MAC

Regarding reporting, I know about adding the 'BUG:' tag to the title, but it's just that I think it's a bit pretentious to think that if something doesn't work is because somebody else didn't do their job correctly, and not because maybe I don't know how to do it. Until recently I had the backups turned on but have never had to revert to using one so have now turned them off as the clutter in the directory was annoying wrote: EAGLE crashes so rarely during normal usage that I don't recall the last time I lost a significant amount of work as a result of a crash and I test out new versions in isolation to ensure they don't have issues before working on a project with them. They are also automatically backed up remotely on iCloud which works and doesn't get all confused with the presence of a #. I work on a specific part of a design, save it and commit with a meaningful commit message and then push it. Personally, I find having my project folder as a GIT repository and making sure I save and commit at regular intervals and push to a remote repository works quite well. Hopefully they'll implement this at some point and then this problem will be easily fixed. I did make a suggestion a few weeks ago that the location of the backups be configurable, that way you could move the backup folder to somewhere not on DropBox so you still have your backups but they are no longer in a place that confuses the cloud storage tools (where the actual bug lies). I've been bitten in the back by crashes enough times to know that I need them and that I won't save often enough.Īs you wish, they were just suggestions which may have helped if the original issue was really bugging you. At least you know that something is wrong and might find a better way to handle backups. In this case, the workaround is worse than the problem I prefer to click the OK button, and then the save button than having to write a script that fixes the issue (I always print this and put it where I can see it ). I normally prefix my title with either 'Feature Request:' or 'EAGLE vx.y.z Bug:' to make them obvious and stand out amongst the other posts as not being just a query on how to do something. If this is what is causing the issue I guess as a work around you could either turn off the generation of backup files, or move your files to another folder and have an automatic script which copies them to your dropbox folder, move do a different cloud storage provider, or maybe use GIT and push your local commits to a remote wrote:Īs a nontopic, is there a better channel to submit errors and bugs?

ERROR 32 WHEN TRYING TO SET FILE TIME FOR MAC

I know it works fine with iCloud for mac machines and I think GoogleDrive works ok too but I haven't tested it extensively. I know there is a similar issue with EAGLE files stored on OneDrive, they changed the backup extension to use $ instead of # for a version to try to compensate until it was pointed out this kills scripts on Mac/Linux and they reverted it. Could it be that dropbox is interfering with the files? Why does then saving the file work? I work on a dropbox folder to backup up my files. Has anybody have an idea of why could this be happening? I think it could be a permission problem, but that wouldn't explain why it happens randomly. It's not a deal breaker, but it's a bit annoying. If I delete the backup files (s# and b#) it works, and I get no error. If I press esc and don't save, and try again, the error will prompt again. Then I get the normal 'save as' dialog, where I can just press 'save' and carry on. Since at least the two or three last versions of Eagle I'm finding a problem where, when I save a file (either a schematic, a board or a library) and Eagle prompts an error saying that it can't rename the 'name of the file.~~~' to 'name of the file.relevant extension'.

Error 32 when trying to set file time