Issue 75743 - new Chart: complex table will give default chart - should be disabled
Summary: new Chart: complex table will give default chart - should be disabled
Alias: None
Product: Writer
Classification: Application
Component: editing (show other issues)
Version: 680m206
Hardware: All All
: P4 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
: 89303 89304 (view as issue list)
Depends on:
Reported: 2007-03-26 12:39 UTC by michael.ruess
Modified: 2013-08-07 14:44 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 michael.ruess 2007-03-26 12:39:20 UTC
Currently, creating a chart from a complex table (where some cells are
merged/splitted) in Writer is not allowed (Insert.Chart is disabled).
In the CWS chart2mst3 this is not the case and the default chart is created.
This will of cause lead to misunderstandings by the user.
Comment 1 bjoern.milcke 2007-03-26 12:47:42 UTC
->TL: The behavior should either be like in the old implementation. I remember
something about an "IsComplex"-function which no longer exists. Looks like we
would need something similar.

Note that chart2mst3 can no longer be used for committing changes at the moment
as it is "ready for QA". Unless we get the CWS back we cannot do any further
fixes (except as patches which are attached at the issue).
Comment 2 andreas.martens 2007-03-26 13:30:22 UTC
After integration of CWS chartmst3 will have to rethink about chart and complex
See related issue 75742 
Comment 3 IngridvdM 2007-04-04 15:24:38 UTC
changed prio to 4 as the scenario is rather seldom
Comment 4 IngridvdM 2007-04-18 15:48:31 UTC
changed target according to i-team decision
Comment 5 Martin Hollmichel 2007-09-10 13:15:38 UTC
move target to 3.x according
Comment 6 michael.ruess 2008-05-14 11:14:42 UTC
*** Issue 89304 has been marked as a duplicate of this issue. ***
Comment 7 michael.ruess 2008-05-14 12:23:36 UTC
*** Issue 89303 has been marked as a duplicate of this issue. ***