Issue 63253 - upper bound of graphics cache should not be constrained
Summary: upper bound of graphics cache should not be constrained
Status: CONFIRMED
Alias: None
Product: General
Classification: Code
Component: ui (show other issues)
Version: OOo 2.0.2
Hardware: PC Windows XP
: P3 Trivial with 4 votes (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords: usability
Depends on:
Blocks:
 
Reported: 2006-03-16 13:03 UTC by m_schnei
Modified: 2013-02-07 22:33 UTC (History)
3 users (show)

See Also:
Issue Type: ENHANCEMENT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description m_schnei 2006-03-16 13:03:15 UTC
In the options, section "General"->"Memory", I want to use 1GB for graphics
cache. This is not possible: My written values are always reduced to 256MB. I do
not think that it is useful to constrain this value: The user has to know
himself, what it is good for him. E.g, I sometimes create graphics-loaded
presentations which many slides. Therefore a higher value might make sense, and
it's ok, because I own a 4GB Athlon64 machine.
Comment 1 Olaf Felka 2006-03-16 13:22:20 UTC
reassigned
Comment 2 jbf.faure 2009-12-01 08:41:11 UTC
I suggest to 
- remove this upper-bound or to set it to something like 50% of available RAM 
- and to set the default value of graphics cache to 25% of available RAM.
Indeed many users are not aware of this configuration option so they encounter
difficulties when they want insert several pictures or photos in a document.
They do not know that it is possible and useful to reduce the size of their images.
As a result they just have a bad user experience, simply because they do not
know the existence of an option.

Regards
JBF