TOPMOST is not a cure-all. What you really want is for the PAUSE or DIALOG to be MODAL to the PARENT window (PARENT = The form from which the pause or dialog was issued).
We are already half-way home on this issue, since to make the PAUSE or DIALOG modal to the parent window, you have to know the HANDLE of the parent and RBase does expose the HANDLE property of its forms. So if you were going to ask for an enhancement, you would want to be able to pass the HANDLE of the form to the PAUSE or DIALOG. DIALOG is a no brainer, since it already accepts multiple arguments. The PAUSE would have to be reconsidered. Likely you would leave the PAUSE as it now exists and opt for an Enhanced PAUSE that would accept arguments in a similar fashion to the DIALOG command. ----- Original Message ----- From: "James Bentley" <[email protected]> To: "RBASE-L Mailing List" <[email protected]> Sent: Tuesday, May 01, 2012 1:38 PM Subject: [RBASE-L] - Re: pause dialog boxes going behind form I agree with Karen. It should always be "top most." Jim Bentley American Celiac Society [email protected] tel: 1-504-737-3293 >________________________________ > From: "[email protected]" <[email protected]> >To: RBASE-L Mailing List <[email protected]> >Sent: Tuesday, May 1, 2012 12:35 PM >Subject: [RBASE-L] - Re: pause dialog boxes going behind form > > >I'm not sure the reasoning behind a TOPMOST property. It should always be >"top most", shouldn't it? Would you ever want it to be behind something, >waiting for a response and not visible? > >Karen > > > >In a message dated 5/1/2012 12:28:35 PM Central Daylight Time, >[email protected] writes: > >>>> >>Maybe we can request an enhancement for pause/dialog to also have the >>TOPMOST property ? >><<< >> >>I am with you; it would be a very welcomed enhancement. >> >> >> >>Javier >> >> >> > > >
