Sure thing. I'll do that shortly!
Ana, as far as checking memory goes, I'm really a newbie, so I'm just
looking at the Process list in the Task Manager. I'd love to know a more
accurate way, because I know that only shows part of the information.
-Tim
On 8/27/2012 1:50 PM, Steven Caron wrote:
great news!
tim can you log some issues on the github page? simply asking for the
example python file to contain this attribute and another for an
example showing how to check for other instances of your pyqt app?
this type of plugin really is just a connection of two APIs, knowledge
of qt and how its APIs are essential, but in this case i would like to
provide in the examples python file a hint as to how to avoid this
issue you encountered.
s
On Mon, Aug 27, 2012 at 11:41 AM, Tim Crowson
<[email protected]
<mailto:[email protected]>> wrote:
Ah! I think that works, Ana! The ram is almost completely freed up
when the window is closed now. A small percentage remains, but
nothing like before. I can't thank you enough!
-Tim
On 8/27/2012 1:24 PM, Ana Gomez wrote:
Tim! I think I know what it is happening. You are right, your
window is not being destroy when you close the window.
Write this on the init of your window:
'self.setAttribute(QtCore.Qt.WA_DeleteOnClose)'. Check the memory
again and open several times the window, close it and open it.
--
--
Signature
