summaryrefslogtreecommitdiff
path: root/officecfg
diff options
context:
space:
mode:
authorZolnai Tamás <tamas.zolnai@collabora.com>2014-11-18 17:37:53 +0100
committerZolnai Tamás <tamas.zolnai@collabora.com>2014-11-18 17:39:15 +0100
commitdbdacc73ae154237314d599194cc686bd738a9bf (patch)
tree3acf345112daf0fa201fcfab5e5ef6e5016acc32 /officecfg
parent7dcfafc7d2f7ce8357c1570ea7547b5879f54172 (diff)
Be honest about the maximum cache size
Implementation uses a multiplicator of ten. I guess the intention here was that to calculate cache size based on the size of the inserted images and not based on the real memory usage (potentionally more instances of one image), which seems a bad idea because it covers the real memory usage from the users (who will be suprised when LO's memory usage increases tenfold of the set value). It seems better to use the exact value in the implementation and increase the default value on the user interface instead. Change-Id: Ie3c0568d3518922d3a9931f894eebb9e7e5515ed
Diffstat (limited to 'officecfg')
-rw-r--r--officecfg/registry/schema/org/openoffice/Office/Common.xcs2
1 files changed, 1 insertions, 1 deletions
diff --git a/officecfg/registry/schema/org/openoffice/Office/Common.xcs b/officecfg/registry/schema/org/openoffice/Office/Common.xcs
index e19df23e094c..fec8d259cbe0 100644
--- a/officecfg/registry/schema/org/openoffice/Office/Common.xcs
+++ b/officecfg/registry/schema/org/openoffice/Office/Common.xcs
@@ -1466,7 +1466,7 @@
objects.</desc>
<label>Total Graphic Cache Size</label>
</info>
- <value>22000000</value>
+ <value>220000000</value>
</prop>
<prop oor:name="ObjectCacheSize" oor:type="xs:int" oor:nillable="false">
<info>