Hi thereI observed a strange behaviour in EA class diagrams. After modifying a diagram (adding class, modifying relation etc), the diagram is locked in a way, that i cannot move elements anymore. I can still add relations, add members to classes, but I cannot MOVE anything on the diagram.

After waiting some minutes, the diagram is unlocked in some magical way, and without any further notice, I can do everything again...Did anybody observe this behaviour aswell?I installed the latest version 909 and it still appears...

I succesfully preset our users EA settings via a .reg file.Now I want to uncheck the option "Generate methods for implemented interfaces" but I cannot find it nowhere in the registry. Does anybody know where it is located?

Hi thereThis is a known problem, and is not related to EA. You have to open tortoise repobrowser in your working copy. If you have to enter your credentials (username/password) make sure you activate "save username". EA is dependent on the configured (and saved) credentials in the working directory. If the repository cannot be accessed with the stored credentials, it hangs and crashes...

Hi thereI have the problem that upon opening of an .eap project, EA prompts me to configure the version control settings. I do this, the paths are saved correctly and i can work normally. When I close and reopen EA, the settings have not been saved and I have to reconfigure everything. What is wrong?

Hi thereI observed a strange behaviour in EA class diagrams. After modifying a diagram (adding class, modifying relation etc), the diagram is locked in a way, that i cannot move elements anymore. I can still add relations, add members to classes, but I cannot MOVE anything on the diagram.

After waiting some minutes, the diagram is unlocked in some magical way, and without any further notice, I can do everything again...

I was really hoping that the issues with VC and xmi imports would be fixed in the Version 9, but we are having lots of troubles, some issues are even worse!

Example:Each time when we do a GetAllLastest, we have to double check our diagrams to see if there are any dependencies that became "External reference". Then the hassle begins... we can redo GetAllLastest and it doesn't help. We have to manually figure out, on which package to do a GetLatest and suddenly the "External reference" relations are gone.

We cannot trust EA that after a GetAllLatest, our model is in a correct state...

So now its getting really bad: So you had no way to resolve the "External References". After deleting these relations, you recreate them and check in your changes, thinking that all will be well... When you're teammate does a GetAllLatest the next time, he gets your newly corrected relations along with the the "External References" you just removed...

Maybe Sparx spent time to modify the import of XMI, but I can tell one thing: It's far from done! We are loosing so much time trying to keep our models intact, its a real pain!

And as soon as I report a bug to Sparx, they want an example project, to reproduce the issue. Well, when you have a distributed system with a central VC (SVN) and lots of packages, its not that simple. I can't send our whole development environnement...

Anybody else out there struggeling with VersionControl in the team environnement?

During the GetAllLatest operation, I noticed several times, that in the progress window, it shows a line telling "Error ...." but I never managed to read the full content, because the operation went on. So I know that somewhere something is wrong, but I have no clue what EA is complaining about...

PLEASE! Add a simple logging functionality, that prints in the System Message window all the packages that have been imported during a GetAllLatest operation. Please dump the filename, package name the repository version and eventual problems. This can't be such a big thing. And it would help us to at least verify which packages were updated, determine which classes were replaced etc.

Actually we were having troubles when NOT doing a force Reload from XMI, we used to have missing dependencies and even missing classes. After starting to use the forced reload (twice in a row), things went somehow better. But as a matter of facts, with both methods we end up from time to time with models that were corrupt.

Since we encountered this issue with both methods, there this fear of never knowing when its going to happen next.

Worst of all, there is no evidence or message alerting that something could be missing, not logfile, just nothing. It can happen that only some time later (and after lots of modification and check-ins/outs) we get aware that something must have been lost on the way. And from that point on, its a real pain to reconstruct things...

We discovered a serious bug concerning the retrieval of packages from SourceControl.When doing a GetAllLatest in a model, I want that all package XML files are retrieved from SourceControl and (forced) imported into my model. This should replace all model elements with the ones that are read from the files.When I randomly choose a package afterwards and do a "Compare with Controlled Version", there are differences showing up. I can do as many GetAllLatest as I want, it doesn't change.Only when I do a GetLatest of the particular package, the package is finally imported and the content replaced. An subsequent "Compare" shows that no more differences are detected.

This bug must have been introduced in one of the latest releases...

The GetAllLatest functionality is not very stable anyway. We used to call it twice always to make sure that all packages and dependencies have been resolved.

After doing a GetAllLatest it happens that some of my controlled packages contains themself once again...

The structure before updateing:

Parent1- Child1- Child2- Child3

The structure after updating:

Parent1- Child1 - Child1- Child2- Child3

Furthermore the version of Child1 and its contained Child1 are not the same...

The only way to get back to the previous setting is by checking out the parent package, removing the Child1's and reimporing them via ImportModelBranch. This works around it until the next time the bug strikes and the package is doubled again...

Anybody else observed this behaviour?

Update:After the appearence of this bug, when I try to do GetLatest on the upper Child1 package, EA gives the following Error message: