Dear Group,
When looking at all the observations and after having read thru all your
responses (thank y'all!) I was convinced that my problem is
card/driver/driver setting related.
In dispair I tried one last thing and opened the adapter property panel,
pushed every "reset to factory defaults" bu
prüngliche Nachricht-
Von: John Wright [mailto:[EMAIL PROTECTED]
Gesendet: Mittwoch, 28. Mai 2003 14:36
An: [EMAIL PROTECTED]
Betreff: Re: [JAVA3D] weird behaviour creating a Canvas3D from a swing
app
Hans,
Sure sounds like a video driver bug to me. I've seen dozens of these
type of odd q
Hans,
Sure sounds like a video driver bug to me. I've seen dozens of these
type of odd quirks (not just with Java 3D). Sounds like your work
around is to use a more standard video mode or upgrade the Voodoo card.
I'd be shocked if Sun Engineers gave you any other response than "it's
probably a v
Yet another data point: I'm using a non-standard resolution (1792*1344)
onmy voodoo3.When I switch to UXGA (1600*1200) the problem goes
away.I've been using that high res since I bought the card a few years
back.Another interesting thing: everything behaves
fine ONCE after switching back to
Alessandro, John,
when run on my home machine, your TestCanvas3D class does the same as my
contrived Test program I had posted earlier.
It gets a Invalid fifoTypegd error (hwcExecuteStatusWinFifo) and goes into
an infinite loop virtually freezing my machine.
As far as the graphics drivers are con
Thus perhaps a video card driver issue?
My suggestion was not meant to be a button was simpler than a menu, my
concern is with the fact that in your example ANY action event will
generate a Canvas3D.
Other potential ideas:
Switch back to a non-beta JDK.
Replace the fairly obsolete Voodoo card
John,
I admit, the example is not the simplest possible that exhibits the problem.
Using a button instead of a menu would have been simpler.
However, the purpose of the example was to create a simplified mock-up test
case that exposes
the same problem as my real app (where indeed I'm doing somethi
Your example never adds the Canvas3D to the JFrame, that seems odd to
me.
To debug it further I'd suggest you try using a button instead of the
menu (once debugged then go back to your menu). And have the
actionPerformed method only create a Canvas3D if the button is the
source of the event. (per
j3d folks,
I'm interactively (via menu selection) creating a Canvas3D from a swing
application;
depending on the size of the application frame I'm experiencing a very weird
problem.
this is a skeleton app that exposes the problem :
import java.awt.event.*;
import javax.swing.*;
import javax.med
