Hello,
Great program...I ran into an error talking about the text file wasn't formatted correctly. The result was that I lost all my top level division headings...it kept all the sub-note entries though...
Any ideas?
jason.
|
Hello,
Great program...I ran into an error talking about the text file wasn't formatted correctly. The result was that I lost all my top level division headings...it kept all the sub-note entries though...
Any ideas?
jason.
I should clarify the previous thread...I got the error when I hit "R" to refresh.
it just happened when I opened it this morning...the error is the same...something is triggering the error and it proceeds to remove all hierarchy...
when I copy over the re-organized file with a good version of the backup...it works fine and doesn't try to remove the hierarchical tree...
I should note that the program created, thus accepted, the backup and its format...
jason.
I managed to create a repeatable sequence of events that will trigger the hierarchical melt down....when I added a sub-note, then deleted the sub-note....this is doing it every time...
Ok, I will look into this. Good that you have a repeatable sequence. So every time when you add a sub-note then proceed to delete it immediately it will delete all the headings correct?
That's it...the program doesn't crash...it deletes all the headings and lumps everything together. I can send you the before and after txt files to look at if you want?
Jason.
Steve,
Have you ever encountered a situation where the Keynote Manager erases everything in the text file? It has happened to us a few times, usually at the worst of times. I can't figure out why or come up with a repeatable sequence to cause this.
I have gotten scattered reports of large chunks of the file being deleted, but never the whole thing. So far I haven't been able to figure out what's causing it, so I haven't been able to fix it. If you can figure out what you did to make it happen I would be very appreciative...
In the mean time, remember that the program makes a backup copy on the users computer every time you open the file, so if this does happen you should have a recent backup to go back to. Also, the backup is per user, so if you have multiple people working on the keynote file, you probably have several recent backups to try...
Thanks Steve. And thanks for the explanation on the back-ups. I always wondered why there were multiple back-ups that appeared to be identical.
Someone at AU first mentioned this to me and I have seen it myself recently. It appears to be linked to multiple people writing back to the file at the same time. If you finish editing while the file is not idle it tends to throw the file all out of whack, lose parent grouping or delete parts of the file.
Is there anyway that the program can wait to write back if the file is not idle?
Nick