🚀 go-pugleaf

Alex,
I'm catching the attempted close w/ the VetoableChangeListener, and providing
an opportunity for the programmer to stop the close w/ another method, as
follows:

public class MDISheet extends JInternalFrame implements
VetoableChangeListener{
 ...
//VetoableChangeListener Implementation
 public void vetoableChange(PropertyChangeEvent evt) throws
java.beans.PropertyVetoException {
    boolean continueClose = true;

    //if sheet is trying to close (VetoableChangeListener receives other
types of notifications, as well...)
    if (evt.getPropertyName().equals(IS_CLOSED_PROPERTY) &&
(Boolean)evt.getNewValue() == Boolean.TRUE) {
      //allow stopping of close process via sheetClosing method
      continueClose = sheetClosing();
      if (continueClose) {
        //do whatever needs to be done before the close continues
      }
      else
      //sheet close was stopped in sheetClosing method, throw
PropertyVetoException to be caught by
      // object that initiated the close of the sheet
        throw new PropertyVetoException("", evt);
    }
  }

//method that users of MDISheet should code to allow/disallow closing of
JInternalFrame
public boolean sheetClosing() {
    //return true to allow sheet to continue closing
    //return false to prevent sheet from closing
    return true;
  }
}

Not sure what's up w/ the internalFrameClosing method, but this alternate
method seems to work alright, if not quite as elegantly as the 'real' method
should...

I had a similar problem w/ the openFrame method of the DefaultDesktopManager
- (_it's_ at least documented that the event doesn't typically trigger...
:-), so I had to make a call from the JInternalFrame to the DesktopManager of
the parent frame's DesktopPane to permit generic handling of opening of a
JInternalFrame.  These are the only real glitches I've come across thus far,
though - overall, I like the JInternalFrame/JFrame/DesktopManager deal. :-)

Jim



"Alex Tavera V." wrote:

> How is your implementation of the VetoableChangeListener?
>
> I have the same problem with the Internal clossing event.
>
> Thanks.
>
> Alex
>
> Jim Stoll <jestoll@crtnet.com> wrote in message
> news:37BC1CBA.312E939F@crtnet.com...
> > It's happening in both 1.1.6 and 1.2.2 - kinda screwy.  At this point,
> > I've got it all setup to use a VetoableChangeListener and it's working
> > alright, so while I'm a little bummed, I'm willing to roll w/ it.
> >
> > Thanks for the info,
> >
> > Jim
> >
> > Michael H�rtig wrote:
> >
> > > Hi,
> > >
> > > Which JDK do you use??
> > >
> > > I think until 1.2.1 it is a official bug (can't remebmber the Bug-ID)
> > > But I got a eMail from Sun and the say in 1.2.2 it is ok. But I don't
> > > tested it.
> > >
> > > Michael
> > > --
> > >            ////
> > >           (o o)
> > > +-----ooO--(_)--Ooo---------------------------------------+
> > > |                                                         |
> > > | Michael H�rtig                 Neumann & Partner        |
> > > |                                Informationssysteme GmbH |
> > > | Softwareentwicklung            An der Hohen Stra�e 1    |
> > > |                                08393 Meerane            |
> > > |                                                         |
> > > +------------Oooo-----------------------------------------+
> > >         oooO (  )
> > >         (  )  (_)
> > >          (_)
> >