Edit sources with EA is risky business

[Stringer]

For some unknown reason our server quite often cuts connection temporarily to shared Windows-network files. Since our intranet PHP-files reside there, it quite often also means that EA (or any other program) is temporarily unable to write changes to these files.

Other well made programs just ask different file name and/or path when error in saving occurs, but what does EA do? Well, it just loses all changes and pretend everything is OK. Actually only thing where you can tell something is wrong, is the timeout delay and the fact that the sources don't appear to the source-window before connection is good again.

For clarification.. I don't mean the EA project file which probably causes more problems, but the original source code files of the project.

[thomaskilian]

You should report this as bug to Sparx.

To circumvent this: how about (semi-automatic) code generation on the server itself. With a shared repository you should be able to have an EA instance run inside your network. Code gen could be done on request manually or via automation.

[Stringer]

Hah, it sounds like shooting insects with a cannon I don't even have two licenses. Besides, code generation hasn't failed even once (who knows why, mayby luck). My problem is related to situation where you open the integrated source editor and edit something manually. I have already circumvented that with external text editor, but sometimes it would be nice to make very small modifications using the source code window.