<string>Maximum number of tiles kept in memory:</string>
</property>
<property name="whatsThis" stdset="0">
<string>The maximum number of "tiles" that are kept in memory. For regular RGBA8 images, each tile is about 16 kB in size. Thus, for a value of 500 tiles this usually means about 8 megabytes are used for image data. If you regularly handle large images, a greater value here might be useful.
Note that this number is only a guideline for Chalk, and is not guaranteed to be the actual number of tiles in memory.</string>
</property>
</widget>
<widget class="KIntNumInput">
<property name="name">
<cstring>m_maxTiles</cstring>
</property>
<property name="value">
<number>500</number>
</property>
<property name="minValue">
<number>0</number>
</property>
<property name="whatsThis" stdset="0">
<string>The maximum number of "tiles" that are kept in memory. For regular RGBA8 images, each tile is about 16 kB in size. Thus, for a value of 500 tiles this usually means about 8 megabytes are used for image data. If you regularly handle large images, a greater value here might be useful.
Note that this number is only a guideline for Chalk, and is not guaranteed to be the actual number of tiles in memory.</string>
<string>This configures how much Chalk will use the swap file. If you move the slider all the way to the left, Chalk will not use the swap file at all. If you move it all the way to the right, Chalk will make maximum use of the swap file.</string>
<string>This configures how much Chalk likes to swap. Move the slider to the left, and there is no swapping at all. Move it to the right there is a lot of swapping going on.</string>