Issue 55572 - Line Transparency seetings mixed up for custom styles
Summary: Line Transparency seetings mixed up for custom styles
Status: CLOSED DUPLICATE of issue 55330
Alias: None
Product: Impress
Classification: Application
Component: formatting (show other issues)
Version: OOo 2.0
Hardware: PC Windows XP
: P3 Trivial (vote)
Target Milestone: ---
Assignee: christian.guenther
QA Contact: issues@graphics
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-10-06 17:04 UTC by helpman
Modified: 2005-11-28 13:20 UTC (History)
1 user (show)

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


Attachments
Presentation with two custom styles (10.07 KB, application/vnd.sun.xml.impress)
2005-10-06 17:07 UTC, helpman
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description helpman 2005-10-06 17:04:23 UTC
If I create custom styles within a presentation, the line style transparency
settings becom inverted after closing and re-opening that document.
Example:
Create a rectangular box, and create a new style. Assign a lign color and assign
this style to the box. The line style dialog displays 0% transparency for the
line (which is what I want.) Close and re-open the document: The line becomes
invisible, because now the line style dialog for the assigned style now shows a
transparency of 100%.
Now enter 1% transparency for the line style. Close and re-open. Bingo - now the
line style transparency is set to 99%
My guess: For some reason, when opening a document, the transparency for the lin
style is calculated as something like '100 - current transparency setting'. 
PLease fix since I don't want to re-assign all tranparency values over and over
again.
Comment 1 helpman 2005-10-06 17:07:58 UTC
Created attachment 30186 [details]
Presentation with two custom styles
Comment 2 wolframgarten 2005-10-07 08:02:27 UTC
Reassigned.
Comment 3 wolframgarten 2005-10-07 08:03:22 UTC
Priority changed.
Comment 4 helpman 2005-10-13 16:46:20 UTC
This is probably the same issue as in 55330 and 55847
Comment 5 christian.guenther 2005-11-28 13:20:08 UTC
You are right.
It's duplicate to issue 55330

*** This issue has been marked as a duplicate of 55330 ***
Comment 6 christian.guenther 2005-11-28 13:20:54 UTC
I close this issue as duplicate.