Re: Splash Screen Woes or Why doesn't setVisible(true) protect from setVisible(false)
- From: "James Kimble" <jkimble@xxxxxxx>
- Date: 28 Jul 2005 10:52:17 -0700
Thank you, this was very helpful.
The app is starting the window in one thread and then spawning a new
thread where the hide window method is called. I believe this is a
problem.
In addtion the setVisible(false) must not be called too quickly after
the setVisible(true). I found that a delay of 500 ms is enough but less
than that (on this platform at least) leads to a white screen that
persists and never
goes away.
Thank you again for the FAQ. It's very helpful.
James Kimble
.
- References:
- Splash Screen Woes or Why doesn't setVisible(true) protect from setVisible(false)
- From: James Kimble
- Re: Splash Screen Woes or Why doesn't setVisible(true) protect from setVisible(false)
- From: Thomas Weidenfeller
- Splash Screen Woes or Why doesn't setVisible(true) protect from setVisible(false)
- Prev by Date: I translate the 2D graphics object, but it prints new and old graphics on each page
- Next by Date: Another Focus Issue with JTable
- Previous by thread: Re: Splash Screen Woes or Why doesn't setVisible(true) protect from setVisible(false)
- Next by thread: Focus Issue with regards to JTable
- Index(es):