cmdrfunk wrote:Any time I make any changes in the visual editor the designer can take anywhere from 10 seconds to FIVE MINUTES to apply the changes.
cmdrfunk wrote:The Fedora Project is taking over the consumer-level part of the redhat distribution. It's still supported by redhat, just not officially. In effect, it's redhat 10 with a new name.
cmdrfunk wrote:The .log file doesn't have any exceptions in it. I even deleted it and ran Eclipse and the plugin again for a few minutes, adding 3 buttons, which took me about 7 minutes to do on a blank form. Wow that's slow
cmdrfunk wrote:Adding items to a ToolBar is taking minutes again, making X unresponsive to mouse presses or key presses until it's done.
javaDev wrote:The cause of the problem appears to be related to instances when I have switched from the visual designer to the source and made manual code updates. Initially, there was no problem with this but now I am encountering situations where, if I am in the visual designer, no matter what change I make however minor causes the class to perform a lengthly regeneration of source. It is manifested as a flashng program icon in the Windows taskbar with the name of the shell. This can take 10 seconds to a few minutes, and often will not complete correctly at all. In WSAD 5.0 the entire IDE would exit with a JVM termination code 128. In WSAD 5.1.1, I will get a stack trace error and a recommendation that I close WSAD. This is happening OFTEN.
javaDev wrote:I have tried bumping up the JVM memory to 64, 128, and 256. However, from observing the task manager, it is CPU not memory that redlines.
javaDev wrote:I have been trying to modify the IDE preferences to control the frequency of regeneration.
javaDev wrote:The error is happening in the visual designer when I try to interact with anything - buttons, text, groups, composites, etc.
javaDev wrote:Only that window so far.
Users browsing this forum: No registered users and 1 guest