Thank you for reporting this bug. We will make it our priority to review this report.
-
-
Hey elgs -
We are still investigating this and have been unable to reproduce.
Do you have any additional information for us from the ticket you filed the other day?
http://www.sencha.com/forum/showthre...er-disappeared
If you can reliably make it happen, perhaps we can do a remote web session this week so that we can see it happen and figure it out.
-
-
Sencha Premium Member
I think I got some more information about this problem. It seems like it's the svn commit caused the references to be lost in the SA. I observed the following situation happened:
1, Open my SA project, work with it for a while, without any problem;
2, Save and publish the SA project. The publish target folder is managed by Eclipse/Subclipse(an eclipse based svn client);
3, Commit all changes to the SA project to the svn repository, including the project files and published files in Eclipse;
4, Now when I come back to SA, the reference to the controller is lost;
I guess at this moment, if I accidentally saved the SA project, I may permanently lose the files.
And I guess svn client should only do write access to its own .svn folder. If this is the case, what I'm wondering is whether SA monitors all files under its project folder, or only the relevant files?
-
SA monitors all of the metadata files and the overrides. I'm going to try to reproduce this issue.
Apologies elgs but are you windows or os x I forget?
-
-

Originally Posted by
elgs
Now whenever I want to do an svn commit, I quit SA, after the svn commit, I open SA again, the problem does not appear anymore.
Great this is good info for us. Sounds like SVN might delete the file and then re-add the file. Our filewatching capabilities probably detect the delete and then update the inspector.
-
Sencha Premium Member

Originally Posted by
aconran
Great this is good info for us. Sounds like SVN might delete the file and then re-add the file. Our filewatching capabilities probably detect the delete and then update the inspector.
I believe this should be the root cause. Now I deliberately and temporarily delete a file from the metadata folder, the reference gets lost. However, the reference is restored when I put back the file from the trash. I guess the trash-put-back triggered an event that is monitored by the SA file watcher, while the svn delete-readd may have done more sophisticate operations that does not trigger any event that SA file watcher monitors. Anyway, close-and-reopen the SA when I want to do an svn commit is totally acceptable for me.
By the way, I want to appeal for a feature request for the code auto format. When the project gets larger, formatting the code manually is painful. What I do sometimes now is copy/paste all my code to Eclipse, format the code with Eclipse and copy/paste back. I think this will make SA a real IDE.
Thanks.
-
I'm actively trying to reproduce the issue now. Are you able to see entries in the log stating files were removed?
http://cl.ly/image/3z34090Q3F0w
-
I cannot get it to reproduce with CrudGenerator at all.
Svn should not be altering the files themselves in any way but only the metadata under .svn.
Let me know what you're seeing in your log