Well, thank you for the interest of the problem.
My friend,as you can see is using Widnows XP
http://nnaass.com/bug/overlep3.jpg
Aslo my wife's computer which is running XP having the problem(but in a less
degree).
Thanks
[Message sent by forum member 'alaamurad' (alaamurad)]
I didn't test this issue in a linux box, but from the thread you can see that
there is a problem in applets (especially in large applets that needed to be
scrolled )
You may need to review the screen shots to see what we are talking about in
this thread.
I don't see any difference between
Dmitri ,
As you could see from the screen shots:
http://nnaass.com/bug/overlep5.jpg
http://nnaass.com/bug/overlep6.jpg
I'm running firefox.I uninstalled the 1.6.10, I thought the latest stable
version of java (1.6.5) will fix the problem but it didn't , I went even
further and I uninstalled
of the page, and I saw this bug before. Unlike flash,
it solid and it's able to repaint itself in
synchronization with the page (even while scrolling
I don't understand what you mean by solid, or with synchornized painting with
the page.
I don't see any difference between flash and java plugin
Thanks for trying.
I have no doubt that it is a bug, I'm just not convinced who's =)
Is your friend using Vista as well?
Dmitri
[Message sent by forum member 'trembovetski' (trembovetski)]
http://forums.java.net/jive/thread.jspa?messageID=268864
First, thanks for the quick reply , I thought the problem only with the JDK
6u10 early access but I had a friend that just installed the latest JRE from
java.com and here are his screen shots:
http://nnaass.com/bug/overlep3.jpg
http://nnaass.com/bug/overlep4.jpg
Another thing regarding the
here is my 2D.log
[I] OS Version = OS_VISTA or newer
[E] D3DPPLM::CheckForBadHardware: found matching hardware: VendorId=0x8086
DeviceId=0x
[E] D3DPPLM::CheckForBadHardware: bad hardware found, device disabled
[E] D3DPPLM::GDICheckForBadHardware: no suitable devices found
I guess it's
[EMAIL PROTECTED] wrote:
here is my 2D.log
[I] OS Version = OS_VISTA or newer
[E] D3DPPLM::CheckForBadHardware: found matching hardware: VendorId=0x8086
DeviceId=0x
[E] D3DPPLM::CheckForBadHardware: bad hardware found, device disabled
[E] D3DPPLM::GDICheckForBadHardware: no suitable
Another thing - is that blinking rectangle (the one that
shows the currently selected handle) done via
xor paint mode? If so, it would slow things down
on systems with Direct3D pipeline enabled because
xor operations are not accelerated (6635462).
It would work ok for smaller areas
