9bd5e75b95
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 |
||
|---|---|---|
| .. | ||
| bmpmaker | ||
| inc | ||
| langsupport | ||
| prj | ||
| qa | ||
| source | ||
| util | ||
| AllLangResTarget_svt.mk | ||
| CppunitTest_svtools_filters_test.mk | ||
| Executable_bmp.mk | ||
| Executable_bmpsum.mk | ||
| Executable_g2g.mk | ||
| Executable_langsupport.mk | ||
| JunitTest_svtools_unoapi.mk | ||
| Library_hatchwindowfactory.mk | ||
| Library_svt.mk | ||
| Makefile | ||
| Module_svtools.mk | ||
| Package_inc.mk | ||
| README | ||
Tools on top of VCL. Common dialogs, file and print dialogs, wizards, vcl filters, lots of helper code.