Version: svn (using KDE KDE 3.5.1) Installed from: Ubuntu Packages Compiler: gcc 4.0.3 OS: Linux For background color : - Create a first style ('style 1'), then change the background color for this style - Create a second style ('style 2'), then select 'style 1' in the inherits box the background color is then different from 'style 1', and worse if I change the background color of 'style 2', the inheritence seems broken, meaning change in 'style 1' aren't propagate to 'style 2'
Works fine here. I think it could be an usability problem: If you create/modify a style, finish you modifications and leave the StyleManager by clicking 'OK', the default style will be applied, because the selection jumps back to it before. The list box has not the focus, so it could be hardly seen.
yes but even in the 'style manager', 'style 2' have a white backgroud instead of the background of 'style 1', I don't see how it can be usuability problem ? or maybe it is intended that background color can't be inherited between styles.
The background color is inherited?! My steps (correct me, if you did it another way): 1. Open StyleManager 2. New 3. Inherit "None" 4. OK 5. Select "style1" 6. Modify 7. Background: change bg color to red 8. OK 9. New 10. Inherit from "style1" 11. OK 15. OK 16. Select A1 17. assign "style1" 18. Select A2 19. assign "style2" => results in two red cells!
I will update and try again, because following what you do I get red on A1 and white on A2 :(
I have update, and I still have the problem :(
Anybody else who encounters this problem?
Long ago, but while it's still oben... When I worked off the list in #3 I had A1 red and A2 white in kspread 1.5.1. Trying to inherit from style1 later on by modifying style2 fails.
Oooh, following my own steps reproduces the problem. What a shame... There's a difference, if you're selecting "style1" after step 8, which results in an automagically selected "style1" as parent. Investigating ...
can't verify, current trunk crashes when I close or apply in the style manager :/
Thank you for the bug report. As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists. If this bug is no longer persisting or relevant please change the status to resolved.