Mailing-List: contact user-help@pivot.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@pivot.apache.org
Received-SPF: pass (nike.apache.org: domain of gk_brown@verizon.net designates
 206.46.173.1 as permitted sender)
Content-type: text/plain; charset=us-ascii
MIME-version: 1.0 (Apple Message framework v1084)
Subject: Re: Rough equivalent of Swing JOptionPane.showConfirmDialog
From: Greg Brown <gk_brown@verizon.net>
In-reply-to: 
 <ABB90CDC9A08FF49851AC42557795A18079BD71B@USINVMAILB01.ingres.prv>
Date: Tue, 16 Aug 2011 15:47:39 -0400
Content-transfer-encoding: quoted-printable
Message-id: <4B4283D1-7FC5-49E3-A3DD-3844BE0766C2@verizon.net>
References: <ABB90CDC9A08FF49851AC42557795A18079BD2B3@USINVMAILB01.ingres.prv>
 <4E49B81F.9090508@hms.harvard.edu>
 <CAFeFZ4uaUUkHZ=ZCPVoERi4TDarcvxMox-CCw2w+RAmTybaYpA@mail.gmail.com>
 <4E4A0A11.90200@hms.harvard.edu>
 <CAFeFZ4vgL1QxorzZvO0gwwP54sWBcN1-6bhg56WcU20MFnKAcA@mail.gmail.com>
 <4E4AAEA9.9090806@hms.harvard.edu> <4E4AAF95.9050109@hms.harvard.edu>
 <ABB90CDC9A08FF49851AC42557795A18079BD6C3@USINVMAILB01.ingres.prv>
 <0BA2B9EC-4C35-443F-B469-19B8A6BF1D8B@verizon.net>
 <ABB90CDC9A08FF49851AC42557795A18079BD6F6@USINVMAILB01.ingres.prv>
 <DE07516F-077C-45BF-A175-D46CEEAC53CA@verizon.net>
 <ABB90CDC9A08FF49851AC42557795A18079BD71B@USINVMAILB01.ingres.prv>
To: user@pivot.apache.org

Yes. You might be able to do something along the lines of =
DesktopApplicationContext#createDisplay().

On Aug 16, 2011, at 3:38 PM, Roger L. Whitcomb wrote:

> Is it possible to piggy back on top of JDialog and just put Pivot
> widgets on an otherwise blank pane?
>=20
> Roger Whitcomb | Architect, Engineering | Roger.Whitcomb@ingres.com |
> Ingres | 500 Arguello Street | Suite 200 | Redwood City | CA | 94063 |
> USA  +1 650-587-5596 | fax: +1 650-587-5550
>=20
> -----Original Message-----
> From: Greg Brown [mailto:gk_brown@verizon.net]=20
> Sent: Tuesday, August 16, 2011 12:31 PM
> To: user@pivot.apache.org
> Subject: Re: Rough equivalent of Swing JOptionPane.showConfirmDialog
>=20
>> Sorry, my use of "blocking" was not intended to be technically
> accurate.
>> Of course, it has to keep pumping the event loop, which is what makes
> it
>> so tricky.  Actually, the tricky code seems to be in java.awt.Dialog
>> where the modal event loop lives.
>=20
> Right, that's what I would have guessed.
>=20
> But in any case, this sort of behavior would require access to the
> native event queue, which AWT does not provide (and I'm not sure =
should
> be exposed anyway).
>=20
> G
>=20