Hallo Robert,
I saw you first message, but unfortunately the fix for this is not
that easy. If you have only one subwindow, then it would be ok to
clear the buffer if pladv() is called. But this is not true if you
have 2 or more subwindows. Clearing one subwindow with e.g. pladv(1)
doesn't mean that you want to clear the other subwindows, what would
happen if you clear the buffer. This might be no problem for your
case, but we would break the library for all who use subwindows. The
fix I have in mind is to split the buffers depending in what subwindow
we plot. So if we have 4 subwindows, we also have 4 buffers where we
save the plot commands and we can safely destroy one of the buffers if
one subwindow is cleared. It's rather straight forward, but still
needs some time to code, so I put it on my TODO list, but it will need
some time (say weeks to months) until I'll address this problem until
someone else beats me to it.
Regards,
Werner
On 31.03.2009, at 13:14, Robert Pollak wrote:
> [Sorry for reposting this. The first version did not start a new
> thread,
> probably making it quite invisible.]
>
> Hello Werner,
>
> in a December thread, you helped me with clearing a wxPLplotwindow.
> The remaining issue was that in either solution (pladv(0) and
> plclear()) the plot buffer is not cleared, and therefore more and more
> memory is consumed with each replot.
>
> Since I now have to update a plot very often and over long time, let
> me
> ask whether the plot buffer can be cleared to avoid the memory
> hogging,
> short of deleting/recreating the wxPLplotwindow. (This problem
> probably
> has been dealt with already, hasn't it?)
>
> Best Regards,
> Robert
--
Dr. Werner Smekal
Institut fuer Allgemeine Physik
Technische Universitaet Wien
Wiedner Hauptstr 8-10
A-1040 Wien
Austria
email: smekal@...
web: http://www.iap.tuwien.ac.at/~smekal
phone: +43-(0)1-58801-13463 (office), +43-(0)1-58801-13469 (laboratory)
fax: +43-(0)1-58801-13499
|