Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!cs.utexas.edu!uunet!hoptoad!tim
From: tim@hoptoad.uucp (Tim Maroney)
Newsgroups: comp.sys.mac.programmer
Subject: Re: List Manager questions
Message-ID: <8115@hoptoad.uucp>
Date: 25 Jul 89 04:31:52 GMT
References: <8374@bsu-cs.bsu.edu> <227700017@uxa.cso.uiuc.edu>
Reply-To: tim@hoptoad.UUCP (Tim Maroney)
Organization: Eclectic Software, San Francisco
Lines: 22

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.

I can understand having some problems with this -- the various code
communications issues are a bit weird -- but there's really no
incompatibility.  Really, the only problems are (1) ModalDialog doesn't
return an event record, so you don't get the click location and mouse
modifier keys, and have to save them in a filter proc or figure them
out after ModalDialog and (2) the list rectangle has to be inset
fifteen pixels to compensate for any 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.

I don't know of any "incompatibilities".  Difficulties, yes.
-- 
Tim Maroney, Mac Software Consultant, sun!hoptoad!tim, tim@toad.com

"Genuinely skillful use of obscenities is uniformly absent on the Internet."
	-- Karl Kleinpaste on gnu.gcc