[softwarelist] Re: OvationPro and memory allocation
- From: David Pilling <flist@xxxxxxxxxxxxxxxxxxx>
- To: davidpilling@xxxxxxxxxxxxx
- Date: Thu, 13 Jul 2006 14:26:44 +0100
In message <4e45b796delists-nospam@xxxxxxxxx>, Paul Vigay
<lists-nospam@xxxxxxxxx> writes
Looking at the task display, I notice that the application task space for
OvationPro constantly flichers when entering text into an OvPro window.
This would imply that OvPro is claiming and releasing wimp application
memory blocks on a more or less constant basis.
If it is claiming and releasing memory, so what?
When you hit a key in OP, a lot of things can happen. Suppose the line
of text contains an embedded irregular picture frame. All sorts of
claiming/releasing memory and rendering will take then place each time
the text changes.
I agree that in the interests of efficiency OP should not be claiming
and releasing memory on each key stroke if it can help it.
I will have tried to avoid this situation, but it is hard to know
exactly what happens. As has just been said there may be applets loaded
that do things on each key stroke.
So it is hard to answer.
--
David Pilling
email: david@xxxxxxxxxxxxxxxxxxx
web: http://www.davidpilling.net
post: David Pilling P.O. Box 22 Thornton Cleveleys Blackpool. FY5 1LR UK
fax: +44(0)870-0520-941
- Follow-Ups:
- [softwarelist] Re: OvationPro and memory allocation
- From: JMAH van Vredenburch
- References:
- [softwarelist] OvationPro and memory allocation
- From: Paul Vigay
Other related posts:
- » [softwarelist] OvationPro and memory allocation
- » [softwarelist] Re: OvationPro and memory allocation
- » [softwarelist] Re: OvationPro and memory allocation
- » [softwarelist] Re: OvationPro and memory allocation
- » [softwarelist] Re: OvationPro and memory allocation
- » [softwarelist] Re: OvationPro and memory allocation
- » [softwarelist] Re: OvationPro and memory allocation
- » [softwarelist] Re: OvationPro and memory allocation
- » [softwarelist] Re: OvationPro and memory allocation
- » [softwarelist] Re: OvationPro and memory allocation
- » [softwarelist] Re: OvationPro and memory allocation
- » [softwarelist] Re: OvationPro and memory allocation
- » [softwarelist] Re: OvationPro and memory allocation
- » [softwarelist] Re: OvationPro and memory allocation
- » [softwarelist] Re: OvationPro and memory allocation
- » [softwarelist] Re: OvationPro and memory allocation
- » [softwarelist] Re: OvationPro and memory allocation
- » [softwarelist] Re: OvationPro and memory allocation
- » [softwarelist] Re: OvationPro and memory allocation
- » [softwarelist] Re: OvationPro and memory allocation
- » [softwarelist] Re: OvationPro and memory allocation
- » [softwarelist] Re: OvationPro and memory allocation
- » [softwarelist] Re: OvationPro and memory allocation
- » [softwarelist] Re: OvationPro and memory allocation
- » [softwarelist] Re: OvationPro and memory allocation
- » [softwarelist] Re: OvationPro and memory allocation
- » [softwarelist] Re: OvationPro and memory allocation
- » [softwarelist] Re: OvationPro and memory allocation
- » [softwarelist] Re: OvationPro and memory allocation
- » [softwarelist] Re: OvationPro and memory allocation
- » [softwarelist] Re: OvationPro and memory allocation
- » [softwarelist] Re: OvationPro and memory allocation
- » [softwarelist] Re: OvationPro and memory allocation
- » [softwarelist] Re: OvationPro and memory allocation
- » [softwarelist] Re: OvationPro and memory allocation
- » [softwarelist] Re: OvationPro and memory allocation
Looking at the task display, I notice that the application task space for OvationPro constantly flichers when entering text into an OvPro window. This would imply that OvPro is claiming and releasing wimp application memory blocks on a more or less constant basis.
If it is claiming and releasing memory, so what?
- [softwarelist] Re: OvationPro and memory allocation
- From: JMAH van Vredenburch
- [softwarelist] OvationPro and memory allocation
- From: Paul Vigay