Issue 26666 - Symbol Charts: Datapoint Property Dialog: missing tabpages Area and Transparency
Summary: Symbol Charts: Datapoint Property Dialog: missing tabpages Area and Transparency
Status: CLOSED DUPLICATE of issue 105005
Alias: None
Product: General
Classification: Code
Component: chart (show other issues)
Version: 3.3.0 or older (OOo)
Hardware: All All
: P4 Trivial (vote)
Target Milestone: ---
Assignee: IngridvdM
QA Contact: issues@graphics
Depends on:
Reported: 2004-03-18 11:27 UTC by kla
Modified: 2013-02-24 21:21 UTC (History)
2 users (show)

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


Note You need to log in before you can comment on or make changes to this issue.
Description kla 2004-03-18 11:27:39 UTC
In the Charttype Line with Symbols, selected Data Point,  the Tabpages Area and
Transparency are missing.
Comment 1 kla 2004-03-18 11:28:27 UTC
Set Keyword
Comment 2 IngridvdM 2004-03-18 13:11:11 UTC
The behaviour is inconsistent in the old charts implementation. For series you
do not have area and transparancy tabpages, you have them only for datapoints.
For a single datapoint the color on the area tabpage does not work at all,
incontranst bitmap or hatches and transparancy does work.
Maybe we should offer both tabpages always for series and datapoints and take
the datapoint fill color from the area tabpage ... .
Comment 3 IngridvdM 2004-03-24 12:35:12 UTC
changed summary
Comment 4 kla 2004-08-11 09:38:48 UTC
according to
this issue will be set to OOoLater
Comment 5 IngridvdM 2005-09-06 13:47:32 UTC
set target for new chart issues
Comment 6 IngridvdM 2006-03-21 20:17:24 UTC
changed summary to start with 'new chart: ' to avoid confusion with regular
chart issues
Comment 7 bjoern.milcke 2006-06-23 10:02:29 UTC
Changed target to 2.x
Comment 8 IngridvdM 2007-04-18 16:36:21 UTC
Changed prio according to i-team decision
Comment 9 IngridvdM 2007-09-11 15:49:21 UTC
changing target because of limited resources
Comment 10 IngridvdM 2008-07-22 14:20:47 UTC
reset to new
Comment 11 IngridvdM 2009-09-16 17:40:43 UTC
I think this should be fixed together with issue 105005.

*** This issue has been marked as a duplicate of 105005 ***
Comment 12 IngridvdM 2009-09-16 17:41:53 UTC
closed as duplicate