Hello Georg,
Good report. I tested your application with JDK 1.4.0 & J3D 1.3 beta 2 and was able to duplicate the problems. I wonder why your canvas gets repainted when you move your mouse on top of it. Mine didn't before I added a mouse handler for the canvas that did the painting.
First I also thought that my problem was coming with both java and javaw. I was launching the application with the InstallAnywhere launcher (lax). I configured the configuration file to use java instead of javaw but I still got the problem, but when I launched the application with plain java, I didn't have it.
Have you thought about any ways to overcome the problem? I have tried to override the paint method in the frame containing the canvas, but it doesn't help. I think it is a timing problem. Repaint or a "focusGained" event should start a thread that would do the painting after a while. Doesn't sound very nice to me.
I wonder if anybody else can reproduce these issues?
Pasi
-----Original Message-----
From: Discussion list for Java 3D API
[mailto:[EMAIL PROTECTED]]On Behalf Of Georg Rehfeld
Sent: 7. toukokuuta 2002 3:47
To: [EMAIL PROTECTED]
Subject: Re: [JAVA3D] Java 3D 1.3 Beta2
RE: [JAVA3D] Java 3D 1.3 Beta2Dear List,
over the weekend I installed JDK 1.4.0 and Java3D 1.3_beta_2 which went
fine, thanks J3D team.
I'm experiencing a paint() problem similar to that reported by Pasi
Paasiala ('covered part of Canvas3D goes gray').
I verbosely report this, because I get part of the error even with JDK
1.3.1 and the possibly related Bugs ...
4665482 - Missing first paint() event under JDK1.4 windows version
4458337 - Merlin: repaints do not work by using javaw on WinNT if
double buffering is disabled
4664490 - REGRESSION: AWT window background isn't drawn on win32 using
javaw
... all name JDK 1.4.0 as the possible source of the bug.
The problem only shows up when 'javaw' is used, not with 'java'. Similar
problems with J3D 1.2.1 did not show up. You'll find a small application
attached for evaluation.
My setup:
- PIII 700MHz
- 320MB Mainmemory
- W2K, Servicepack 2
- nVidea Riva TNT with 16 MB Memory, AGP
- JDK 1.4.0 (build 1.4.0-b92) and
- JDK 1.3.1 (build 1.3.1-b24)
- J3D 1.3 beta 2, OpenGL
Observations with JDK 1.4.0 (build 1.4.0-b92):
1a. Click on 'Action' to pop up menu, release, then click again --> the
Menu disappears, then release ==> a gray area appears where the menu
was. Move the mouse over the Canvas3D --> gray area disappears
1b. Select 'Action/New Shape (grid 0.02)' to generate many points and
drop the framerate. Repeat step 1, but this time do the second
click/release really fast, so that both fall into the same render
frame --> the error does NOT show up.
1c. Open the 'Action' menu again, then click/release any menu item
(including the noop one), don't move the mouse yet --> the menu
disappears OK, eventually new content is displayed. Now move the
mouse ==> a gray area appears where the menu was and 1 (or few?)
frames later disappears, causing flicker.
2. Overlap the 3D application partly with some other window, then switch
back to it, either by ALT-TAB or by moving the mouse into the title
bar and clicking --> the 3D content is repainted OK. Move the mouse
anywhere into the menu area of the 3D app ==> a gray area appears
where the other window overlapped. Move the mouse over the Canvas3D
--> the gray area disappears.
3. Resize the 3D app --> the Canvas3D correctly is repainted. Move the
mouse into the menu area without moving over the Canvas3D ==> the
whole Canvas3D goes gray. Move the mouse over the Canvas3D --> canvas
gets repainted.
Observations with JDK1.3.1 build 1.3.1-b24
1a. Click on 'Action' to pop up menu, release, then click again ==> the
Menu disappears but a gray area is left behind; release ==> gray
area remains; move mouse to Canvas3D --> repainted OK. This behavior
does not show up always (~70% of the cases, sometimes mouse movement
in the menu area and/or opening the 'File' menu forces the error).
Could never reproduce bug with many points/low framerate.
1b. from above does not show up.
1c. Open the 'Action' menu again, then click/release menu item 'New
Shape (grid 0.02)' forcing many points/considerabe computation
time/low framerate --> the menu disappears, a gray area is left
behind until J3D repaints to all black then ==> the gray area
flickers up for one frame again sometimes (20% of the time).
I consider this acceptable, but report it for completeness.
2. Overlap the 3D application partly with some other window, then switch
back to it, by ALT-TAB --> the 3D app is repainted OK just once.
Again overlap and switch back, this time by moving the mouse into the
title bar and clicking ==> often (50% of the cases) the Canvas3D is
noticably repainted twice: grey area visible, repainted, gray area
AGAIN visible, then finally repainted. Most visible with medium
frame rate/medium number of points.
3. Resize the 3D app ==> the Canvas3D often (>50% of the cases) gets
repainted twice as with 2. above. Again most visible with medium
frame rate/medium number of points.
Conclusion
Though with JDK 1.4.0 the bugs are more and more obvious, it seems to
me, that the cause is not only in JDK 1.4.0 but partly somewhere in J3D.
I hope my observations can help fix the bugs.
Best regards
Georg
___ ___
| + | |__ Georg Rehfeld Woltmanstr. 12 20097 Hamburg
|_|_\ |___ [EMAIL PROTECTED] +49 (40) 23 53 27 10
----- Original Message -----
From: Pasi Paasiala
To: [EMAIL PROTECTED]
Sent: Thursday, May 02, 2002 1:26 PM
Subject: Re: [JAVA3D] Java 3D 1.3 Beta2
We seem to have a slight problem with Java3D 1.3 beta2.
What happens is the following:
When I put a window on top of the window containing the Canvas3D and then bring the frame with the canvas to top again by clicking
on on the window title bar, I get the scene full rendered, but once I move the mouse to the canvas, the part that was covered goes
gray.
If I then move the camera, the rendering is fine again.
[...]
