Re: [AQT-dev] memory, window control

[Per P. <per...@ma...>]

 
On Monday, May 12, 2008, at 02:00PM, "Marius Amado-Alves" <ama...@gm...> wrote:
>Operation aqtClosePlot does not close the window, so I assume it is
>only to free memory structures not required for the window.

Yes. Basically it balances the aqtOpenPlot() call. 
It causes the command queue to be flushed and the finalized image to be rendered.
Furthermore, it is no longer possible to access that plot's data, nor will events be passed from the plot to the client.

Wether or not the window is actually closed when aqtClosePlot()  is called depends on a preference setting:
Preferences->Window Closing->Client Controlled
If checked, the window will close with the aqtClosePlot() call (possibly after user confirmation depending on the other checkbox)

>
>Anyway, is it possible to control the window operations
>programatically, for example close, resize, save as PDF?

No, by design. My original intent was that the client should have no knowledge about GUIs, windows, and pdfs, etc. Then again, there is the event mechanism so I guess the other parts could be rethought too.

/Per