Printable View
i am working weeks on an aplication and tonight i complited the work and after reboot, i am traying to open my aplication but i am getting :cannot copy data elemt! and right after that faild to open document..what the [expletive deleted]..can i fix this?
:( :( :(
This happens often... you really need to backup.
But if you haven't and you really need it back; i would ask an admin... a while back i had (i think it was Yves) fix a corrupt file for me :grin:
Good luck
Send Yves a PM and see what he says.
But as always .... you should make backups of your work.
Few do it but many have wished they had.
Just a suggestion: I think by default it should have the automatic backup turned on. Could just be my opinion though.
With build 248 -- MMF suggests you have it turned on :)
I use a product called Mozy that uploads my data everynight to a backup off site server. I have lost too many files to bad backups and no backups so this is the only thing that works for me :)
Counting on myself to backup never worked.
Every day once I finish working on a project I make a copy of the entire project folder and name it by date, I also have 3 autobackups on and once a week I mirror all my project files and program files onto an external drive.
I have had too many corrupt applications to take a risk.
thanks for the support at this bad hour :(
pm'ed to Yves and no..i don't have auto backup probably, cause i am working with the HWA beta.
luckily i have old backup so i will not have to start it all over again, but still..i forgot what i have done already lol..
its very big thing that all the media i created lately is safe too.
Use an automated backup tool then. There are plenty of decent, free tools (e.g. my favorites being filehamster and syncback).
[color:#CC33CC]*Dynamite makes a copy of his big project[/color]
I must admit, I loved TGF 1.06's auto-backup feature, which rolled back to the last time you ran the application. Dunno why that ever got removed, it was such a useful feature (nudges Clickteam).
It would be immensely useful if MMF had an optional file management system, where you could save your applications using filenames and versions instead of the traditional file/folder method.
For instance, I make a new file and it gets automatically named 'Untitled Application', and its version is set to 0.0. I make a few changes, click SAVE and it becomes 0.000001.
Each itteration would store a separate file. Eventually, the app reaches a certain stage, so I click a new button, called Version Up, which lets me mark this one off as a new version, like 0.001
So your version numbers may go:
0.000001
0.000002
0.000003
...
0.000021
0.000022
0.001
0.001001
0.001002
...and so on. Basically, giving you the option for MMF to handle the versioning for you, and have clearly marked higher and lower versions.
It would file these away in its own folders and subfolders, archiving and compressing old copies, perhaps only recording alterations (using code from Patch Maker perhaps?).
It could store key files, like an animation stores keyframes. Those key files are maintained in their entirety, and subsequent versions are recorded as patches to adjust the previous key file (so in our case, version 0.001 would be saved as a key file, and 0.001001 would be saved as a patch to it).
If ever MMF decides that the most recent patch is resulting in a corrupted, unreadable file, you could simply keep rolling back until you found a working one. Since it's based on patches, and you're never overwriting the original, the probability of a serious corruption is drastically reduced.
After a while, MMF could prompt to collapse old mini versions into one patch, saving space. Or convert some of the older keys into patches if they're very similar to earlier keys. Or simply delete the history after a certain point.
I think that'd be ossum! :)
So what you're asking for is that MMF has it's own revision control system..
Why don't you just use an existing one? (e.g. subversion or filehamster)
i dont believe the feature(auto-backup) was removed......check under the preferences menu...
after every save to an MFA, MMF should do an integrity check on that MFA to make sure it saved correctly, and alert the user if it didn't
the main reason i don't use autobackup is because you don't know a file has become corrupted until you try to reopen it; you can easily do hours of work on a file that became corrupted at some point without you knowing, and saving it enough times that your entire backup cache is corrupted
Do revision systems like Subversion or File Hamster handle your file the moment you save it, without you having to fiddle around with a dialog? This is what I was hoping for when making that sugegstion.
Backing up isn't the problem, it's backing up at the right time, and in a way that isn't more hassle. You can have versions which are only 10 mins apart, but if the corruption occurred between that point, and you've lost a crucial and very complicated expression that you now can't remember, the result is as soul destroying for me as losing an hour's work.
You need a backup system which is totally seamless, and can be relied upon to intuitively record your work when you most need it to.
The answer's "sort of". Normally you have to actively commit something after a change (which makes sense for source code as it may go through several iterations before you have something meaningful), but it's possible to autocommit through scripting the command line version.
http://gael-varoquaux.info/computers/svnautocommit/index.html#the-autocommit-script
The answer ain't "sort of". FileHamster can make a revision the second you press save. Although I prefer it to check not more often than every minute.
You can specify how much time between each revision should be waited (for those who press save every 10 seconds, like me). So if you set that time carefully, you have enough revisions to not lose too much work.
Clearly, the answer's much better than "sort of"!
When I tried file hamster I couldn't get it set up properly to backup on a save, I was probably just being thick though, lol.
Delay_CreateRevision is the value you want to set low then. It's how long it should wait between revisions. Don't forget to set up the initial revision for your file or it won't work. Although by default it automatically asks you to create one.