[wxPython] wxCalendar

[Lorne White]

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

[Rene Freund]

hi,

Lorne White wrote:

> 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:

thx, but i use the old Calenderdlg.

i took all controls from the oldone and design a new one... with 2
calenders. the second one should be able do disabled. that works.
the calendar window (the whitewindow) is disabled but the user can't
see it. is no good.
i use an own dialog, with a panel so i can't use this solution
but thx for your help. i hope i read you in a couple days.

i have time to eliminate this problem, it isn't very important yet.

thx reen <--is a german kid

----
Rene Freund nur ein toter bug ist ein guter bug
re...@meder.de

[F. Oliver Gathmann]

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: ogat...@cri-inc.com

[Prabhu Ramachandran]

hi,

Well it doesnt happen under Linux (wxPython 2.2.5, Python 2.1)

prabhu

>>>>> "FOG" == F Oliver Gathmann <ogat...@cri-inc.com> writes:

FOG> Hello all, I just noticed that, on my Win2000 machine with
FOG> wxPython 2.2.5/Python 1.5.2, the little app below eats about
FOG> 150K every time you push the button (i.e., the process size
FOG> as indicated by the task manager is increased by that
FOG> amount). Evidently, the memory used by the wxMemoryDC
FOG> instance is not freed when the Python instance is deleted. Is
FOG> there anything I don't know about DC's in wxPython or is this
FOG> a bug?

[Robin Dunn]

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

> _______________________________________________
> wxpython-users mailing list
> wxpytho...@lists.wxwindows.org
> http://lists.wxwindows.org/mailman/listinfo/wxpython-users
>

[F. Oliver Gathmann]

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

--