Newsgroups: comp.lang.smalltalk
Path: cantaloupe.srv.cs.cmu.edu!rochester!udel!gatech!newsfeed.internetmci.com!in2.uu.net!netnews.jhuapl.edu!aplcenmp!dmalks
From: dmalks@aplcenmp.apl.jhu.edu (T Malks daniel brand 2028221432)
Subject: Re: [VW2.5] window-event question
Message-ID: <Do7twJ.8rC@aplcenmp.apl.jhu.edu>
Organization: Johns Hopkins Continuing Professional Programs
References: <4i5fag$ouv@noc.tor.hookup.net>
Date: Wed, 13 Mar 1996 17:00:18 GMT
Lines: 34

quenton@Cherniak.ON.CA (Dennis Smith) writes:

>I needed to trap a window resize (by the user).
>On resize, I needed to adjust Table column sizes
>(different sized columns, some fixed and some variable).

>The code to do that took under an hour.  Trapping the resize
>event took the rest of the day.

>Here is what I ended up with:

>        aBld window sendWindowEvents: #(#resize).
>        aBld window receiveWindowEvents: #(#resize).
>        self expressInterestIn: #windowState for: self sendBack: #adjust. 
>        aBld window application: self.

>The problem seemed to be that the ApplicationWindow would not
>pass the event on if it went to its own applicationModel.  That was
>why I had to go lower level and use "expressInterestIn:...".
>I would have prevered to use ApplicationWindow/Model level
>methods.

>Does anyone have a better solution?

Perhaps I misunderstand your intent, but why not override/extend
ApplicationWindow>>processEvent: ?

Hope this helps:)
Danny

-- 
Daniel Malks
Congressional Quarterly, Inc.   dmalks@cqalert.com
Johns Hopkins University        dmalks@aplcenmp.apl.jhu.edu
