I don't believe this is a bug. This is a
performance limitation of
non-opaque windows on Windows platform - there's
nothing we can
do about it. Non-opaque windows were not originally
intended for
windows with high update rate. Every update means
that we have
to update whole window
[EMAIL PROTECTED] wrote:
I don't believe this is a bug. This is a
performance limitation of
non-opaque windows on Windows platform - there's
nothing we can
do about it. Non-opaque windows were not originally
intended for
windows with high update rate. Every update means
that we have
to update
To let the user decide to enable such an option is OK.
However I think possibly there still exists a performance bug. The test case
below causes an avererage of 5% CPU utilization for opaque window and 50% CPU
utilization for non-opaque windows even if the animated panel is placed on an
opaque
even if the animated panel is placed on an opaque panel
This doesn't matter. If the window is made non-opaque,
then every component inside that window will have to
pay the price.
I don't believe this is a bug. This is a performance limitation of
non-opaque windows on Windows
Thanks for the info.
Wolfgang
[Message sent by forum member 'wzberger' (wzberger)]
http://forums.java.net/jive/thread.jspa?messageID=287672
===
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the
Hardware info for the older machine:
[code]
[I] OS Version = OS_WINXP Pro
[I] CheckAdaptersInfo
[I] --
[I] Adapter Ordinal : 0
[I] Adapter Handle : 0x10001
[I] Description : NVIDIA GeForce2 MX/MX 400 (Microsoft Corporation)
[I] GDI Name, Driver : \\.\DISPLAY1, nv4_disp.dll
That is indeed a rather old board. I think it may not
be the board that's slow but the bus between the
cpu and vram - since non-opaque window send a bunch
of data on every repaint from system memory to
vram, the bus speed is very important.
The only suggestion I have is to provide
Java 6u10 provides a method to modify widow opacity. On older machines, I
assume without hardware acceleration, setting a window to the non-opaque mode
leads to a very high CPU utilization. I wonder if there is a way to check the
availability of hardware acceleration?
Tested with Java build
[EMAIL PROTECTED] wrote:
Java 6u10 provides a method to modify widow opacity. On older machines, I assume without hardware acceleration, setting a window to the non-opaque mode leads to a very high CPU utilization.
HW acceleration is actually disabled for the window
with opacity 1.0 on
Thanks for the info.
The problem is that my test app works fine on a modern machine with Vista and
non-opaque window mode. On an older machine with XP the app is too slow so the
additional eye candy which is provided by the non-opaque window mode should not
appear.
That's why a auto-detection
[EMAIL PROTECTED] wrote:
Thanks for the info.
The problem is that my test app works fine on a modern machine with Vista and non-opaque window mode. On an older machine with XP the app is too slow so the additional eye candy which is provided by the non-opaque window mode should not appear.
11 matches
Mail list logo