[5255] in java-interest
AWT kludges in 1.0
daemon@ATHENA.MIT.EDU (Andruid Kerne)
Sat Feb 3 23:53:52 1996
Date: Sat, 3 Feb 96 22:26:16 EST
From: andruid@SLINKY.CS.NYU.EDU (Andruid Kerne)
To: java-interest@java.sun.com, aaviad@netvision.net.il
In-Reply-To: <199602031441.GAA26838@java0.javasoft.com> (owner-java-interest-digest@java.sun.com)
>>>
I have no idea if this is intended or a bug but note that this exception =
will happen even if you do not call getGraphics() directly but by way of =
calling repaint() on (say) a TextField force the ScreenUpdater to send =
an update(Graphics g) to this Component which in turn requires a =
getGraphics() call.
This is one of the unfortunate design errors that AWT seem to have. =
There is a complete imbalance in the implementation of native =
components. The programmer that attempts to subclass any of the non =
Canvas components will find out that the Win32 implementation will paint =
it's own controls without calling back into the Java code. This will =
prevent any special effects or changes to the painting of these =
controls.
>>>
yeah, i noticed this stuff in the release notes.
it looks like they just ran out of gas on the Windows port, and
decided to hack the documentation, instead of the code or the api!
(i believe the operative phrase is, "that's not a bug, its a feature." :-))
perhaps due to bad planning they *can't* make that part of the Java api
work right under Windows.
i hope y'all at Sun clean this up, cause its ugly.
--
Regards,
Andruid Kerne
NYU Media Research Laboratory
--and also--
Creative Media Cauldron
http://c4dm.nyu.edu/andruid/
The distinctions between artists and engineers -- between content
developers and programmers -- are entirely artificial.
-
This message was sent to the java-interest mailing list
Info: send 'help' to java-interest-request@java.sun.com
