Seth Spitzer <[EMAIL PROTECTED]> writes:
> > When deleting doesn't cause scrolling, I don't think we suffer the same
> > > performance problems.
>
>this really seems to be the case. try this:
>task #2 is much slower than task #1.
>
>using the tree batching APIs we can get #1 ~= #2.
>tree batching will also make "select all, delete" faster, too.
>
>My guess is if we are going to two 2 or more scrolls, we should do batching.
Any chance of getting this into Bookmarks as well?
--
Randell Jesup, Worldgate Communications, ex-Scala, ex-Amiga OS team ('88-94)
[EMAIL PROTECTED]
- tree batching: performance fix for multiple message delete... Seth Spitzer
- Re: tree batching: performance fix for multiple messa... David Bienvenu
- Re: tree batching: performance fix for multiple m... Seth Spitzer
- Re: tree batching: performance fix for multip... Seth Spitzer
- Re: tree batching: performance fix for mu... Randell Jesup
- Re: tree batching: performance fix f... Chris McAfee
- Re: tree batching: performance f... David Bienvenu
- Re: tree batching: performan... Seth Spitzer
- Re: tree batching: performance fix for multiple messa... Alec Flett
- Re: tree batching: performance fix for multiple m... Seth Spitzer
- Re: tree batching: performance fix for multip... Alec Flett
- Re: tree batching: performance fix for mu... Chris Waterson
