Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!haven!umd5!zben
From: zben@umd5.umd.edu (Ben Cranston)
Newsgroups: comp.sys.mac.programmer
Subject: Re: List Manager questions
Summary: Also must fudge activate/deactivate events?
Message-ID: <5129@umd5.umd.edu>
Date: 25 Jul 89 21:36:27 GMT
References: <8374@bsu-cs.bsu.edu> <227700017@uxa.cso.uiuc.edu> <8115@hoptoad.uucp>
Reply-To: zben@umd5.umd.edu (Ben Cranston)
Organization: University of Maryland, College Park
Lines: 27

In article <227700017@uxa.cso.uiuc.edu> jpd00964@uxa.cso.uiuc.edu writes:
> I also had horrid problems putting a list in a modeless dialog box.  Most
> of my problems were alleviated when I did as much as possible outside of
> the filter proc.  There is some incompatability, and I do not know where.

In article <8115@hoptoad.uucp> tim@hoptoad.UUCP (Tim Maroney) writes:
> ... the only problems are (1) ModalDialog doesn't return an event record...
> ... (2) the list rectangle has to be inset fifteen pixels for scroll bars. 
> As long as you install a userItem procedure with the proper call to LUpdate, 
> and make sure the scroll bar lies inside the userItem as described in (2),
> the whole thing works quite well.

Tim, the user was talking about MODELESS dialogs and you are talking about
MODAL ones.  Nevertheless, I basically agree that it pretty much works.  One
area I have had trouble with is activate/deactivate, which only happens in
the MODELESS case (you cannot put a MODAL dialog into background or indeed do
ANYTHING until you satisfy it).  The dialog manager KNOWS about TextEdit so
it can deactivate and activate any included TextEdit items in response to the
corresponding event.  It does NOT know about the List manager in this way,
so I found I had to manually check for these two events and manually call
LActivate (before the IsDialogEvent/DialogSelect stuff as I recall).

Other than that, I have had no trouble with lists in modeless dialogs...
-- 
Sig     DS.L    ('ZBen')       ; Ben Cranston <zben@umd2.UMD.EDU>
* Computer Science Center Network Infrastructures Group
* University of Maryland at College Park