Ryan Heise wrote:
> If ScreenSaver extends Window, we don't need ...
a) it doesnt
> > private Graphics2D g;
>
> Graphics handling can get messy if you keep a reference to your own
> graphics context. There was once a problem with a Windows JVM where you
> could not have open more than 5 or 6 graphics contexts without exceeding
> the resource limit. Graphics contexts are intended to be short term
> objects. They are also intended to be used from within the AWT thread -
> I'm not sure exactly what could go wrong if you don't but I could
> imagine swing getting confused. It likes to manage Graphics contexts
> itself since most of the graphics handling stuff is written in Java
> (instead of native peers).
b) Ive realized this and have changed the class
> If you extend Window, you will inherit a similar method. It may sound
> like I'm suggesting that you extend Window. I don't actually mind. You
> could extend Canvas. You could define an interface with a paint() method
> just like Component. Luckily, the screensaver module is isolated enough
> that you can easily change your design as many times without breaking
> much.
ScreenSaver only extends Object, its not a component
Im writing another e-mail about my update to the SSDK, just wait about 5
minute...
Cheers,
DigiGod
_________________________
[EMAIL PROTECTED]
AIM:DigiGod 86
_________________________
Quote of the Moment:
Thus spake the master Ninjei:
"To the intelligent man, one word, to the fleet horse
one whip, to the well-written program, a single
command"
_________________________
Prank of the Moment:
Using the conferencing feature of your office phone, dial
one Induhvidual, then while it's ringing dial another and
conference them together. Put your own phone on mute
and listen to see how long they'll make small talk before
figuring out that neither one placed the call.
O-
_______________________________________________
UI maillist - [EMAIL PROTECTED]
http://jos.org/mailman/listinfo/ui
