Skip to main content

Java SE 6.0 has smoother rendering

Prior to Java SE 6.0, there were some issues with Swing painting.
  • When a minimized swing window was unobscured, it took a while for it to repaint. Till then the user saw a gray box. I think they also call it the "gray rect" problem :-)
  • Assume that the application is blocking the event dispatch thread (maybe because it is performing a large computation or loading a large file...). If we minimize and application, then it will not show a painted window upon unobscuring untill the event dispatch thread is unblocked. (offcourse we should not block the event dispatch thread for such a large task. Ideally a task larger than 250 ms should be started in a seperate thread)
In Java SE 6.0 these issues are resolved with "true double buffering". Java maintains a buffer that keeps an image of the onscreen window. This buffer is updated whenever the contents of the onscreen window are changed. If we minimize and then maximize the window, the window will not be repainted from scratch, instead it's image from the buffer will be copied to the video memory (using the toolkit thread). This elliminates the "gray rect" problem since the window will be displayed immediately without any time lag. Since the buffer is maintained in the hardware (most likely video RAM), it is true double buffering.

I am not very certain what a toolkit thread is. Will find out, but in the meanwhile if anyone knows, please post a comment.

The fine print:
True double buffering is enabled only on the windows platform at the moment. However it is implemented for other platforms as well, and will be enabled soon.


Anonymous said…
Cool blog

Popular posts from this blog

Five Reasons Why Your Product Needs an Awesome User Guide

Photo Credit: Peter Merholz ( Creative Commons 2.0 SA License ) A user guide is essentially a book-length document containing instructions for installing, using or troubleshooting a hardware or software product. A user guide can be very brief - for example, only 10 or 20 pages or it can be a full-length book of 200 pages or more. -- As engineers, we give a lot of importance to product design, architecture, code quality, and UX. However, when it comes to the user manual, we often only manage to pay lip service. This is not good. A usable manual is as important as usable software because it is the first line of help for the user and the first line of customer service for the organization. Any organization that prides itself on great customer service must have an awesome user manual for the product. In the spirit of listicles - here are at least five reasons why you should have an awesome user manual! Enhance User Satisfaction In my fourteen years as a

Inheritance vs. composition depending on how much is same and how much differs

I am reading the excellent Django book right now. In the 4th chapter on Django templates , there is an example of includes and inheritance in Django templates. Without going into details about Django templates, the include is very similar to composition where we can include the text of another template for evaluation. Inheritance in Django templates works in a way similar to object inheritance. Django templates can specify certain blocks which can be redefined in subtemplates. The subtemplates use the rest of the parent template as is. Now we have all learned that inheritance is used when we have a is-a relationship between classes, and composition is used when we have a contains-a relationship. This is absolutely right, but while reading about Django templates, I just realized another pattern in these relationships. This is really simple and perhaps many of you may have already have had this insight... We use inheritance when we want to allow reuse of the bulk of one object in other

Planning a User Guide - Part 3/5 - Co-ordinate the Team

Photo by  Helloquence  on  Unsplash This is the third post in a series of five posts on how to plan a user guide. In the first post , I wrote about how to conduct an audience analysis and the second post discussed how to define the overall scope of the manual. Once the overall scope of the user guide is defined, the next step is to coordinate the team that will work on creating the manual. A typical team will consist of the following roles. Many of these roles will be fulfilled by freelancers since they are one-off or intermittent work engagements. At the end of the article, I have provided a list of websites where you can find good freelancers. Creative Artist You'll need to work with a creative artist to design the cover page and any other images for the user guide. Most small to mid-sized companies don't have a dedicated creative artist on their rolls. But that's not a problem. There are several freelancing websites where you can work with great creative ar