Lionel Elie Mamane 9bd5e75b95 forcing repaint has catastrophic performance implications; invalidate only ... In Base: 1) Open a big table (hundreds of rows) 2) Only the first 40 to 100 rows are fetched into the cache and shown (depending on screen / window size). 3) Move to last row (click on icon |>|) 4) The last 40 to 100 rows are fetched into the cache; the data of the first 40/100 rows is pushed out of the cache. 5) The first 40 to 100 rows are fetched, just so that the call to rWindow.Paint() can do its job, because they are not in the cache anymore (!). The last 40/100 rows are pushed out of the cache. 6) The last 40 to 100 rows are fetched into the cache and displayed; the first 40/100 rows are pushed out of the cache *again*. Steps 5 and 6 are obviously *very* stupid. Change-Id: Ic11b893ea9440c2c5a142bd3c77c95d6730aa723		2012-07-24 17:35:57 +02:00
..
brwbox1.cxx
brwbox2.cxx
brwbox3.cxx
brwhead.cxx
brwimpl.hxx
datwin.cxx
datwin.hxx
ebbcontrols.cxx
editbrowsebox.cxx	forcing repaint has catastrophic performance implications; invalidate only	2012-07-24 17:35:57 +02:00
editbrowsebox.hrc
editbrowsebox.src	hrc cleanup: Remove include guards from src files	2012-07-14 05:43:47 +02:00
editbrowsebox2.cxx
editbrowseboximpl.hxx