Not quite what I want... I, too, can get multiple windows, and by sending a new java.awt.Frame as the owner argument to DesktopAplicationContext.createDisplay(...) I get a new window that stacks independently from my main application window <hooray!>.
BUT - There is no minimization capability. Not only can't I minimize the secondary display frame (not even programmatically, say within a button Action), it doesn't even "auto minimize" with the main application window (which makes sense since I'm specifically trying to avoid a parent relationship to eliminate stacking restrictions). This leaves me with a "permanently raised" window on the screen (unless I close/terminate/kill it). The best solution I constructed is to have an in-window button whose Action delegate does this: ((MainWindow) source.getWindow()).getDisplay().getHostWindow().setVisible(false); (Which complifikates my application by requiring some other window, e.g. the "truly main window", to be able to turn the visibility back on. I suppose this could be handled using a DisplayListener delegate - but that all seems so... well, complifikated... <sigh>.) I think whole state of affairs is because Pivot is using an extension of java.awt.Dialog (the HostDialog) as the basis for the Display. (Is this to make it work consistently between desktop and applet?). Needless to say, the situation is quite annoying <grrr>. I have no concern about applets for this application (at least not yet). I hope there's something I'm doing wrong or have missed or misunderstood or some secret sauce you can share... TIA PS - Despite this frustration, I'm liking Pivot very much. -- View this message in context: http://apache-pivot-users.399431.n3.nabble.com/How-to-open-two-windows-tp2022668p2637226.html Sent from the Apache Pivot - Users mailing list archive at Nabble.com.
