incubator-ooo-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject DO NOT REPLY [Bug 119277] Area color applied to symbols other than selected one.
Date Wed, 25 Apr 2012 13:25:13 GMT

--- Comment #4 from Armin Le Grand <> 2012-04-25 13:25:13 UTC ---
ALG: Maybe for You as end user the concept was not clear enough; there are not
only styles in a hierarchy applied to the objects (styles and graphic objects
both have parents), th eobject itself can have attributes which are then called
'hard' attributes and win over styles.
New objects have nearly no hard attributes (there are exceptions). When You
edit just styles to make objects look different these will be derived as
Most users work more direct with the selected object. When having a object
selected and using the fill/line style changers (or the color bar) of course
the 'hard' attributes of that shape get changed; you do not want unselected
objects to change.
Unfortunately working with styles is from the concept more complicated than not
having this (our competitors do not), but also much more mighty. Most casual
users do not understand styles at all (not even in text editors). This is not
meant against them, they should not have to know about and normally do not
need; they can do all they intend by using hard attributes.
Seen from the other side this implies that users which work with styles have to
know all about it to succeed, including the hard attributes at objects vs. soft
ones in styles. It would be nice when the styles concept could be offered per
UI to users in a way that everybody will understand them, but at least I know
no possibility to do so. For the casual user it is complicated.

Back to the task: When knowing about hard and soft attributes what happens in
Your example should be understandable from user perspective, too. It may also
be necessary to better describe it in the manuals.

Configure bugmail:
------- You are receiving this mail because: -------
You are on the CC list for the bug.

View raw message