Yes, there are some callbacks missing. I was assuming a standalone dialog
with results.
It shouldn't be too difficult to extend it out, but I'm not sure when I'll
get to it. Give me a couple days.
As for color, there is a default attribute for the Calendar class named
self.back_color = 'WHITE'. This can be controlled for the dialog with the
following change:
dlg = CalenDlg(self)
dlg.Centre()
dlg.calend.back_color = 'color'
if dlg.ShowModal() == wxID_OK:
Lorne White
Hello all,
I just noticed that, on my Win2000 machine with wxPython 2.2.5/Python
1.5.2, the little app below eats about 150K every time you push the
button (i.e., the process size as indicated by the task manager is
increased by that amount). Evidently, the memory used by the wxMemoryDC
instance is not freed when the Python instance is deleted. Is there
anything I don't know about DC's in wxPython or is this a bug?
Any suggestions much appreciated,
Oliver
-----------------------------------------------------------
from wxPython.wx import *
if __name__ == "__main__":
def memoryeater(ev):
for i in range(3000):
c = wxMemoryDC()
app = wxPySimpleApp()
f = wxFrame(None, -1, 'test', size = (30,50))
b = wxButton(f, -1, 'START')
EVT_BUTTON(f, b.GetId(), memoryeater)
f.Show(1)
app.MainLoop()
--
F. Oliver Gathmann, Ph.D.
CRI Inc., 35-B Cabot Road, 01801 Woburn, MA, USA
phone: (781) 935-9099#245, fax: (781) 935-3388
e-mail: ogathmann@cri-inc.com
hi,
Well it doesnt happen under Linux (wxPython 2.2.5, Python 2.1)
prabhu
Hello all, I just noticed that, on my Win2000 machine with
> wxPython 2.2.5/Python 1.5.2, the little app below eats about
> 150K every time you push the button (i.e., the process size
> as indicated by the task manager is increased by that
> amount). Evidently, the memory used by the wxMemoryDC
> instance is not freed when the Python instance is deleted. Is
> there anything I don't know about DC's in wxPython or is this
> a bug?
It doesn't on win2k with wxPython 2.3.0 and Python 2.0 either. Maybe
there's some issue with 1.5.2 there...
RObin
Well it doesnt happen under Linux (wxPython 2.2.5, Python 2.1)
prabhu
> Hello all, I just noticed that, on my Win2000 machine with
> wxPython 2.2.5/Python 1.5.2, the little app below eats about
> 150K every time you push the button (i.e., the process size
> as indicated by the task manager is increased by that
> amount). Evidently, the memory used by the wxMemoryDC
> instance is not freed when the Python instance is deleted. Is
> there anything I don't know about DC's in wxPython or is this
> a bug?_______________________________________________
wxpython-users mailing list
wxpython-users@lists.wxwindows.org
http://lists.wxwindows.org/mailman/listinfo/wxpython-users
Thanks, Prabhu and Robin, this at least tells me I can keep my present
code and move over to new versions of wxPython and Python.
Oliver
Robin Dunn wrote:
It doesn't on win2k with wxPython 2.3.0 and Python 2.0 either. Maybe
there's some issue with 1.5.2 there...RObin
>
> Well it doesnt happen under Linux (wxPython 2.2.5, Python 2.1)
>
> prabhu
>
>
> > Hello all, I just noticed that, on my Win2000 machine with
> > wxPython 2.2.5/Python 1.5.2, the little app below eats about
> > 150K every time you push the button (i.e., the process size
> > as indicated by the task manager is increased by that
> > amount). Evidently, the memory used by the wxMemoryDC
> > instance is not freed when the Python instance is deleted. Is
> > there anything I don't know about DC's in wxPython or is this
> > a bug?
>
>
> _______________________________________________
> wxpython-users mailing list
> wxpython-users@lists.wxwindows.org
> http://lists.wxwindows.org/mailman/listinfo/wxpython-users
>_______________________________________________
wxpython-users mailing list
wxpython-users@lists.wxwindows.org
http://lists.wxwindows.org/mailman/listinfo/wxpython-users
--
F. Oliver Gathmann, Ph.D.
CRI Inc., 35-B Cabot Road, 01801 Woburn, MA, USA
phone: (781) 935-9099#245, fax: (781) 935-3388
e-mail: ogathmann@cri-inc.com