Hei, > But anyway the point of my post was that there is something lacking in > the way OOo currently handles the old fashioned styles. Notably that > darned inheritance blocking... a user should be able to control that > sort of thing.
I'm not quite familiar with the issue. I was assuming it goes back to inheriting when you change the attribute to the value it has on the parent style. But ovviously that isn't the case? I guess i can think of four possible solutions: 1. Same as above, but additionally add a "re-inherit unchanged attributes" button in each dialog. Additionally, mark changed attributes (i.e. by using a different color for their labels). 2. Behaviour as i expected, and mark non-inherited attributes visually. 3. Add an "Inheritance" checkmark for each option. This is doable, since - if consistently done - those checkmarks don't need extra labels. 4. Have the inheritance checkmark in a context menu for each option. Mark changed attributes. 5. Add a listview somewhere that lists all the options with checkmarks for their inheritance. Eventually mark changed options as well. I guess 1. would be the most quickfix type solution, because the basic behaviour wouldn't need to be changed and it adds the possibility to "unblock" style inhertance. I don't see much point right now in having a checkmark on every option or something like that, because the mere action of changing the attribute states a users choice to not inherit the attribute. With that approach, 2. would be sufficient. Well, i know it would be an additional advantage to declare for an unchanged attribute, that it shouldn't be inherited, so that changing the parent later on doesn't affect the subordinate style in that attribute. I guess for that solution 3. would be the best UI choice. 4. is nice because it doesn't add primary UI clutter, but it is adds effort on the coding site. 5. Worst option. It adds redundancy and breaks flow. André.
signature.asc
Description: This is a digitally signed message part
