Hi again, so Dmitri, you would suggest to get the current graphics cinfiguration each time I touch the according image, right. That was the approach I used at the very beginning (as i have shown in one of my code examples here). But still, I have the problem that the call sometimes does not react to a changing graphics configuration on my target system. I assume that you have no idea what to do about that, right.
One more thing to say: When the dialog with the volatileImage in it was moved to the other screen, but the graphics configuration change was not recognized, the CPU load increases immediately. . . -> This leads me to the conclusion, that the image is no more hardware accelerated and that is exactly what I want to avoid. Could it be that somewhere in the background a method is called (in order to get the current graphics configuration) that returns immediately, no matter if the system was able to detect the current configuration or not, and that when the method returns, it returns the same configuration as the last time due to a cached field or something? I am just wondering, how I can solve this problem because the enduser would not understand, why his system slows down sometimes he moves the dialog to an other screen and sometimes it does not slow down . . . . Maik [Message sent by forum member 'kiamur' (kiamur)] http://forums.java.net/jive/thread.jspa?messageID=293203 =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff JAVA2D-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
