Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing
|Summary:||Color of Filled Area (including Notes) resettet upon Config|
|Component:||formatting||Assignee:||AOO issues mailing list <issues>|
|Status:||CONFIRMED ---||QA Contact:|
|Target Milestone:||AOO Later|
|Issue Type:||DEFECT||Latest Confirmation in:||---|
Description mbayer 2008-10-19 18:27:47 UTC
1. Open a new spreadsheet: File -> New -> Spreadsheet 2. Insert a note: Insert -> Note (type in some text) 3. Visualize the note: context menu -> Show Note 4. In the context menu of the note choose Area 5. On the Tab Area choose a colour (or leave it on the yellowish default colour) 6. Click on the Shadow tab 7. Switch back to the Area tab Expected behaviour: Colour chosen in step #5 is still selected. Observed behaviour: Always "Black" (1st entry in the list) is selected. Note that the same error occurs with all Shapes (Drawings toolbar) when you edit them in the way described above, and in both modules, Calc and Writer. OOo 2.4.1 (680m17 B9310) Linux i86 RPM de_DE OOo 3.0.0 (OOO300m9 B9358) Linux i86 RPM de_DE OOo 3.0.0 (OOO300m9 B9358) Windows de_DE
Comment 1 mbayer 2010-12-18 23:11:38 UTC
This still is reproducible with OOo 3.3.0 RC8 (OOO330m18 Build9556) under Linux 64 Bit. But I guess the problem is not located in the spreadsheet component, as the same defect occurs when using the draw functions in Writer or any of the shapes in Draw: Just right-click a shape or a block arrow or something, then click "Area", switch to any tab, then back to tab "Area": the colour is always set to "Black" (first in list), and will be applied when clicking OK. Adjusting component...
Comment 3 wolframgarten 2010-12-20 11:18:51 UTC
Changing the tab should not change the color. Workaround would be not to hit ok but cancel...
Comment 4 mbayer 2010-12-20 21:18:56 UTC
IBTD. Clicking "Cancel" can't be a workaround, as you discard all the changes previously made on the other tabs (shadows, transparency, and so on). Using one tab after an other, and never switching back, could be a workaround... However, I can't believe this won't ever be fixed (because this is what "OOo later" means). If A BROKEN UI isn't a concern, what then?