Re: Callbacks, and using interfaces as arguments
- From: "Mike" <MPBrede@xxxxxxxxx>
- Date: 30 Dec 2005 22:00:26 -0800
IchBin wrote:
> Mike wrote:
> > I have the following code snippets. Both has a method call to
> > addWindowListener
> >
> > It is my understanding that BookOrderFrame is using a callback method
> > to implement the interface for WindowListener. Am I correct?
> >
> > LoanCalculatorFrame otoh, does it substantially different and does not
> > even state "implements WindowListener".
> >
> > So can anyone please explain what LoanCalculatorFrame does and whether
> > and how it is better/worse than what BookOrderFrame is doing?
> >
<snipped code >
> The Docs for WindowListener Interface I think explains it.
>
> The listener interface for receiving window events. The class that is
> interested in processing a window event either implements this interface
> (*and all the methods it contains*) or extends the abstract
> WindowAdapter class (*overriding only the methods of interest*).
>
I am sorry if I didn't explain myself very well. I understand (I think)
what WindowListener interface does. What I don't understand is the
differences in the implementation between the two example classes that
I posted.
.
- Follow-Ups:
- Re: Callbacks, and using interfaces as arguments
- From: Ricky Clarkson
- Re: Callbacks, and using interfaces as arguments
- References:
- Callbacks, and using interfaces as arguments
- From: Mike
- Re: Callbacks, and using interfaces as arguments
- From: IchBin
- Callbacks, and using interfaces as arguments
- Prev by Date: Re: Callbacks, and using interfaces as arguments
- Next by Date: Advantages of using private static methods in a class
- Previous by thread: Re: Callbacks, and using interfaces as arguments
- Next by thread: Re: Callbacks, and using interfaces as arguments
- Index(es):