JAVA & Blinds Response Time !!! Help !!! Please Important

Java Paints super super slow

I have a Java 1.6 application I wrote to handle a Fantasy Football league. The application has various screens/panels. Some panels require you to click a checkbox. Some panels require data entry. The system uses the standard Java Metal Interface and not the Windows interface.

All the screens/panels paint as if the system is running on the web using a 4800 baud modem. For those of you who remember the old BBS running at 4800 baud. Yes that is exactly how the application starts up and runs. When you type One Character on a screen sit back and wait 20 - 30 seconds for that character to show on the screen.

If I tell Blinds 6.1 to NOT skin this application. Nothing happens any different. Works just as slow.
If I turn off Hyperpaint no change. Works just as slow.
If I UnLoad WindowBlinds.. The Speed Returns. Screens paint real time. Characters typed shows up realtime with no delay.

I cannot find a Blinds setting that affects the Java application. The only thing I haven't tried is setting the Java interface to a Windows interface to see if that change anything. I don' think it will

Does anyone else have this problem or does anyone know a fix for this problem.

A side note: I had this same problem with Blinds 5. I stopped using it. I hoped V6 would fix it. Does not appear to.
Any ideas, help, thoughts would be greatly appreciated. I'd hate to have to Unload Blinds every weekend I need to do Fantasy Football stuff.

 

1,684 views 2 replies
Reply #1 Top

Your problem is almost certainly the per pixel alpha + Java issue where updates to the Java UI cause all windows with semi-transparency to flicker.

This is a bug in the JVM

Sun had to fix it for Vista as it caused the dwm to shutdown but I am unsure if they ever released the fix for XP machines as well
You
will likely have the same problem with any per pixel windows such as objectdock, desktopx, cursorfx

Reply #2 Top

Thanks for the update. I am running the more than current version of JAVA 7.10 which is a beta release.

You would think that would have the fix.

I'll look around