[5388] in java-interest
Re: Event and Paint handling in AWT
daemon@ATHENA.MIT.EDU (Amy Fowler)
Wed Feb 7 13:03:27 1996
Date: Wed, 7 Feb 1996 08:19:15 -0800
From: Amy.Fowler@Eng.Sun.COM (Amy Fowler)
To: java-interest@java.Eng.Sun.COM, aaviad@netvision.net.il
Cc: rnielsen@webra.com
>
>>Note that this solves the mystery about Events that are missing from native
applet components. I think that this issue should be on top of the list to fix
in the next round because it makes AWT really non extendible. Note that even the
loss of focus is not passed to a TextField which is really a minimum even if sun
chose to implement only Key Actions.
We are [extremely] aware that the current event model is incomplete
and limits AWT's current extensibility. We do appreciate hearing
about specific problems (i.e. like the focus complaint above)
because it will help us prioritize fixing those problems.
>>
>>Few important issues here:
>>1. Can we expect this issue to be resolved soon?
It's on the list (along with many many other things!) --
we do understand that making AWT flexible and extensible is
one of the highest priorities (right up there with platform
parity).
>>2. Is there a workaround at least to be able to detect the loss of focus (not
by keyboard monitoring because the loss of focus can happen by mouse action) ?
Hummm. I can't think of one off-hand. anyone out there found a way?
>>3. Do the sun people realize that the same problematic functionality hold also
for painting of AWT components? As things stand, we have no way to override
painting of AWT components other then Canvas and Containers. The correct
functinality should be
>>to pass the paint() and update() calls to the Java derived component and let
it invoke the default painting of the native AWT object. I am worried that at
this point, since the API is frozen (for a while) and these methods are 'void'
this is not in sun's plan.
Painting on top of native components is not as straight-forward
as it sounds, although I agree it's important functionality.
>>
>>does anyone have any suggestions? Comments? How about Sun?
The above issues are the result of an extremely aggressive
schedule for 1.0 where there just wasn't time to provide maximum
functionality. We are working very hard (believe me :-) to
resolve the problems to give you all a solid, powerful toolkit.
(in other words, we ARE listening...)
Regards,
Amy Moore-Fowler
Java Products Group
Sun Microsystems, Inc.
-
This message was sent to the java-interest mailing list
Info: send 'help' to java-interest-request@java.sun.com
