diegoesp wrote:When I initiated the tests, I did it opening a real system with 100 classes or so. In those conditions, Designer took a long time to do anything: from changing a property (3 or 4 seconds) to cutting and pasting some widgets (10 or 20 minutes).
How was this file created? With Designer or something else? Can you send us a test case? If we can reproduce the problem, we can either fix it or suggest a work around. A small system with only 100 classes should not pose any issue at all.
As long as Designer is installed properly and Eclipse configured properly, there is no concievable reason that any operation would take more than a second or two. If cutting and pasting a couple of widgets takes 10-20 minutes, then there is a serious problem either with the Designer installation or your Eclipse configuration. When you installed Designer, did you clean your Eclipse "configuration" directory as described in the installation instructions?
diegoesp wrote:I don't see any exceptions in the eclipse log file, and I don't think memory is the problem
What is you exact Eclipse startup command line? I am still concerned that you have configured Eclipse to use
all of your physical memory. If there is nothing in your log pointing to some sort of frequent (and time consuming) exception, then swapping would be a possible explanation for the behavior you are seeing.
diegoesp wrote:By the way, I'm using latest version of Eclipse (3.1) and the latest version of Designer (downloaded just last Wednesday).
In that case, you are definitely not using the most recent version of Designer. v4.1.0 was just released over the weekend. I would suggest the following:
1) Delete
all of the Designer v4.0.1 feature and plugin directories
2) Download and install Designer v4.1.0
3) Delete everything in your Eclipse "configuration" directory except the
config.ini file
4) Change your Eclipse startup command line to something like this: -
vmargs -Xms128M -Xmx256M