[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kwrite-devel
Subject:    Re: About dyn. word warp
From:       Christoph Cullmann <cullmann () babylon2k ! de>
Date:       2002-03-29 19:11:36
[Download RAW message or body]

On Friday 29 March 2002 20:51, Joseph Wenninger wrote:
> Hi
>
> > class KateLineRange
> > {
> >   public:
> >     int line;  // who am I ?
> >     int startCol;  // where does I start
> >     int endCol; // where does I end ;)
> >     bool wrapped;  // be I wrapped
> >     int start;  // in pixel for update
> >     int end;  // same here
> > };
> >
> > and therefor have allready the stuff in it we need ? or does the
> > lineMapping goes wider than the current visible stuff ? if not, we should
> > drop it and merge it with the lineRanges, as they are even faster then
> > the hash as a plain and little array.
>
> With proper range checks for the Ranges that should work, although I'm not
> sure if it is really efficient when invalidating the virtualline-realline
> mapping and the Ranges are allocated always for the complete document,
> which causes some an unnecessary high memory consumption, but it's worth a
> try
Mom, for the whole document ? I thought the ranges would only be needed for 
the at the moment visible line count (I mean endLine-startLine = linecount of 
the current view), why does we need it for the whole document ? can 't we 
recreate it on scrolling/editing from the stuff in the regionTree ? as it is 
done now ?

>
> Kind regards
> Joseph Wenninger
>
> _______________________________________________
> kwrite-devel mailing list
> kwrite-devel@mail.kde.org
> http://mail.kde.org/mailman/listinfo/kwrite-devel

-- 
Christoph Cullmann
Kate/KDE developer
cullmann@kde.org
http://kate.kde.org
_______________________________________________
kwrite-devel mailing list
kwrite-devel@mail.kde.org
http://mail.kde.org/mailman/listinfo/kwrite-devel
[prev in list] [next in list] [prev in thread] [next in thread]