I remove one more duplication of the PropertyChangeSupport thingy in
java.awt.Container. From the specs it is not immediately clear to me why
addPropertyChangeListener is overridden in java.awt.Container. So I let
it call super for now.
2006-02-06 Roman Kennke [EMAIL PROTECTED]
*
Hi,
I'm checking this in on behalf of Ingo Prötel. Basically this makes
Container.visitChild more safe by protecting the Graphics context from
beeing irrevocably changed by the child component. This is similar to
what we do in Swing's painting mechanism and it actually does matter a
little even
Sven pointed out a bug, it was not possible to receive mouse motion
events on a component, that does not have a MouseListener installed.
Here comes to fix.
2005-11-17 Roman Kennke [EMAIL PROTECTED]
* java/awt/Container.java
(findComponentForMouseEventAt): Also check for
Don't create peers for added components if the container doesn't have a
peer yet!
2005-08-14 Sven de Marothy [EMAIL PROTECTED]
* java/awt/Container.java
(addImpl): Call addNotify() only if the container has a peer.
Index: java/awt/Container.java
Don't create peers for added components if the container doesn't have a
peer yet!
2005-08-14 Sven de Marothy [EMAIL PROTECTED]
* java/awt/Container.java
(addImpl): Call addNotify() only if the container has a peer.
Index: java/awt/Container.java