Path: utzoo!attcan!uunet!tut.cis.ohio-state.edu!snorkelwacker!paperboy!husc6!bochner
From: bochner@speed.harvard.edu (Harry Bochner)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Help!
Message-ID: <BOCHNER.90Jan12155938@speed.harvard.edu>
Date: 12 Jan 90 20:59:38 GMT
References: <16747@megaron.cs.arizona.edu>
Sender: news@husc6.harvard.edu
Organization: Aiken Computation Lab, Harvard University
Lines: 23
In-reply-to: gerhard@cs.arizona.edu's message of 11 Jan 90 04:02:51 GMT

In article <16747@megaron.cs.arizona.edu> gerhard@cs.arizona.edu (Gerhard Mehldau) writes:
   (1) I'm trying to use the same DLOG/DITL resource for several
       related dialogs.  This requires that a button be shifted
       slightly before the dialog is displayed.  I'm calling
       GetNewDialog(...) to read in the resources, then
       GetDItem(...) to get the button's handle and
       MoveControl(...) to move the button, and finally
       ShowWindow(...) to display the dialog.  The button
       is drawn in the correct location, but when I do a
       ModalDialog(NULL,...) and try to click on the button,
       the Dialog Manager only reacts if the mouse is in the
       *intersection* of the old and new rectangles.  What
       am I doing wrong?

Seems to me that you're effectively going behind the Dialog Manager back
by calling MoveControl yourself, and that's why it's confused. I don't
have IM in front of me, but I think you should be able to modify the
rect returned by GetDItem, and pass it back via SetDItem, letting the
Dialog Manager call MoveControl itself. Then its idea of where the
button is won't be out of date.

Harry Bochner
bochner@endor.harvard.edu