On Sat, Jan 14, 2006 at 01:38:28PM +0200, Martin Vermeer wrote:
> On Sat, Jan 14, 2006 at 11:12:28AM +0100, Lars Gullik Bjønnes wrote:
> > Martin Vermeer <[EMAIL PROTECTED]> writes:
> >
> > | On Fri, Jan 13, 2006 at 06:01:52PM +0200, Martin Vermeer wrote:
...
> > | Does anyone see a problem wi
On Sat, Jan 14, 2006 at 11:12:28AM +0100, Lars Gullik Bjønnes wrote:
> Martin Vermeer <[EMAIL PROTECTED]> writes:
>
> | On Fri, Jan 13, 2006 at 06:01:52PM +0200, Martin Vermeer wrote:
> |
> | > ...that the method bruteFind() in cursor.C searches the *whole
> | > document*, i.e., *every single ch
On Sat, Jan 14, 2006 at 11:14:28AM +0100, Jean-Marc Lasgouttes wrote:
> > "Martin" == Martin Vermeer <[EMAIL PROTECTED]> writes:
>
> >> How to make it faster? The attached doesn't really help much,
> >> because forwardPar() still calls forwardPos() internally for every
> >> character.
>
> Mar
Martin Vermeer <[EMAIL PROTECTED]> writes:
| On Fri, Jan 13, 2006 at 06:01:52PM +0200, Martin Vermeer wrote:
|
| > ...that the method bruteFind() in cursor.C searches the *whole
| > document*, i.e., *every single character position*, for the best place
| > to drop the cursor!
| >
| > This cause
> "Martin" == Martin Vermeer <[EMAIL PROTECTED]> writes:
>> How to make it faster? The attached doesn't really help much,
>> because forwardPar() still calls forwardPos() internally for every
>> character.
Martin> The attached helps a lot, and is "low hanging fruit".
Did you look at forwardP
On Fri, Jan 13, 2006 at 06:01:52PM +0200, Martin Vermeer wrote:
> ...that the method bruteFind() in cursor.C searches the *whole
> document*, i.e., *every single character position*, for the best place
> to drop the cursor!
>
> This causes a noticeable slowness (several seconds!) when exiting so
