Win a copy of Kotlin in Action this week in the Kotlin forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic

Problems with repainting in 1.4 AWT  RSS feed

Team Timbala
Posts: 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
We are planning to deploy a jre 1.4.x compatible version of our rich AWT client to our 8000 users and as it stands now we are experiencing an issue that is a show stopper.

Previously our product ran under Microsoft�s jview (where our product was very stable). Under jre 1.4, we are experiencing serious delays and high CPU utilization during the repainting of our screens. Under jre 1.3.x we do NOT experience these problems.
Our application constructs views dynamically by swapping a nested Panel hierarchy in and out of an Applet. We are using the following approach for the repainting of our screens: we iteratively call invalidate() for all the children of a Container and then call validate() on the Container in order to accomplish repainting of said Container.
During this upgrade we are not modifying existing code except for when it breaks 1.4 compilation. Since we didn�t change our approach to repainting for 1.4, is there an approach that is preferred in 1.4? If there isn�t another approach that is necessarily preferred is there an alternate approach of any kind?
We ran Borland�s Optimizeit profiler which reported that during the repaint freeze, 99.16% of the time was spent in the method. Any help would be greatly appreciated. Thank you.
- Team Timbala
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!