fdsdb
|
Hi All,
I am not absolutely sure of I am going to write, but it is at least the third time it seems to me that when I change the name of a patch in a Workspace, or copy and paste in a different folder in my Workspace, when I reopen it, it is totally empty.
Is it possible? If yes, there is a way to recover the missed work?
I am on OsX 10.8.5.
Thanks in advance for suggestions, Best
Fabio
|
anders
|
Hi Fabio!
If possible, could you be very specific, ie. very step-by-step instruction to reproduce the things necessary to make a patch disappear?
Could be some strange naming issue, so perhaps archive an actual workspace and send it along with the above mentioned step-by-step explanation.
We’ll find out what this is about!
Thanks,
-anders
|
fdsdb
|
Hi Anders,
Thank you for reply, sorry for my delay: busied in Conservatory. I am not sure to remember all step-by-step passages, so I will try to be exact much as possible.
I have a Workspace full enough of folders and patches. I was working on a patch denominated “armonici”, with another patch denominated “armonici old”. I have erased the “armonici old” patch, because no more necessary, and then renominated “armonici” to “22 armonici”, inside its folder inside the workspace, but in reopening the renominated patch all objects have desappeared, it was an empty space. That is what I remember.
The same has happened perhaps some other two times with renominated patches.
No problems if there is not solution or explanation, I have recovered all work, importing a patch I had sent by mail, and rebuilding another one by memory.
I have tried to experiment the same procedure with another not important patch, but in this case the patch content has been preserved.
Best
Fabio
|
Jean
|
Hello Fabio,
I think I was able to reproduce and find out what is your problem: the contents of a patch will disappear if you rename it before to open it (that is when its contents is not yet loaded in your OM session).
This is an important bug that I think I introduced myself while fixing another issue with persistant variables (see this other thread).
While working on it, I also spotted another similar bug, if you cut and paste a patch in your workspace before to open it.
I think both bugs should be fixed with the attached patch file.
Please try to put it in …/OM 6.14.app/Contents/Init/, and let me know if anything goes wrong or unusual.
Best,
Jean
|
NM
|
Hi Jean,
I have the same issue. The lisp file has fixed it however I have some .omp files that were affected by this problem before I added your fix that are still opening blank. I’ve tried to copy them and import them as if new files with new names, however these are still open blank. Any ideas to save the contents of these patches?
Thanks,
Nick
|
Jean
|
Sorry I think the contents of these documents is really gone.
I have also lost some patches myself. The only way to get them back is trough your OS, if you have some periodic backup of your file system (TimeMachine or other).
Jean
|
fdsdb
|
Dear Jean,
Thank you for your fix and for remembering my troubleshooting.
I have installed the patch and done some test, it seems to me it works.
To be more exact, about the troubleshooting, I have just reproduced it (before installing the patch), and verified it renaming the patch, cutting and pasting it. If I renamed the patch, copied and pasted it, inner material was preserved. Now, with the fix, everything runs perfectly (no matter of coping or cutting and then pasting the renamed patch), thank you again.
Best
Fabio
|
