[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cp-patches] RFC: AWT painting broken?
From: |
Roman Kennke |
Subject: |
Re: [cp-patches] RFC: AWT painting broken? |
Date: |
Tue, 16 Aug 2005 15:22:19 +0200 |
Am Dienstag, den 16.08.2005, 14:36 +0200 schrieb Jeroen Frijters:
> Hi,
>
> Maybe it's me (I'm always fighting with AWT whenever I work on it), but
> the recent batch of changes to AWT broke painting for me (using my own
> peers).
>
> I don't pretend to understand how this is supposed to work, so it could
> very well be something in my peers, but I think attached patch makes
> sense.
No it does not. The method processEvent is only intended to give
applications with Component subclasses a chance to process the event.
The AWT itself should not do any logic in these methods.
> Basically, it gives the peer a chance to handle any event,
> whether it is enabled or not.
Sorry, I don't quite understand this. The peer actually has a chance to
handle events in the handleEvent() method in ComponentPeer. This should
somehow call Component.update() or Component.paint() in response to
UPDATE and PAINT events respectivly. I have tested this stuff extensivly
against the JDK, which does something similar.
I hope this helps.
/Roman