[carniz]

I have noticed that resizing say, a package with two or three subpackages (and some classes in the inner packages) is awfully slow on a P4 3.2Ghz /w 2Gb RAM running WinXP, using JDK 1.4.2. This is a heritage from ArgoUML I believe, as it behaves exactly the same (has to be related to some sort of checking that’s going on while resizing). If that’s the case, why not disable that check or simultaneous resizing (of all contained objects?) until the user releases/finishes the resizing of the outer object? Just guessing here, haven’t looked into the ArgoUML code.

/Mikael

[Riyad Kalla]

Mikael,
The state of the UML editor is really in “preview” mode right now, we have plans moving forward to Eclipse-i-fy the whole thing and continue to refine it. I have filed your resizing performance issue for us to look at during our tuning pass, thank you.

[Author]

Posts