Issue 61177 - Change of line thickness in diagramm
Summary: Change of line thickness in diagramm
Status: CLOSED DUPLICATE of issue 59598
Alias: None
Product: General
Classification: Code
Component: chart (show other issues)
Version: 3.3.0 or older (OOo)
Hardware: All Linux, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: kla
QA Contact: issues@graphics
URL:
Keywords: oooqa
: 61175 61176 (view as issue list)
Depends on:
Blocks:
 
Reported: 2006-01-26 08:49 UTC by udomerk
Modified: 2013-02-24 21:22 UTC (History)
2 users (show)

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

Attachments
change of line thickness bug sample (16.43 KB, application/vnd.sun.xml.calc)
2006-01-26 09:02 UTC, udomerk 		no flags Details
change of line thickness bug sample (16.43 KB, application/vnd.sun.xml.calc)
2006-01-26 09:06 UTC, udomerk 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description udomerk 2006-01-26 08:49:02 UTC 
This bug refers to ooo 2.0.1 linux only.  
The win version works correctly !  
  
Description:  
make a table in scalc (two rows, 3 lines for example).   
Insert -> diagram -> diagramm type: lines.  
  
If you change the thickness of a line now, you will   
see that suddenly the first and the last datapoint  
are now connected by an additional line !! 
And the thickness is wrong. 
 
I would like to send you a small file showing the bug, 
but up to now I do not know how to upload...
Comment 1 udomerk 2006-01-26 09:02:14 UTC 
Created attachment 33570 [details]
change of line thickness bug sample
Comment 2 udomerk 2006-01-26 09:06:26 UTC 
Created attachment 33571 [details]
change of line thickness bug sample
Comment 3 frank 2006-01-26 09:24:17 UTC 
wrong component, changed to Chart and re-assigned
Comment 4 ace_dent 2006-01-26 12:28:26 UTC 
*** Issue 61175 has been marked as a duplicate of this issue. ***
Comment 5 ace_dent 2006-01-26 12:29:05 UTC 
*** Issue 61176 has been marked as a duplicate of this issue. ***
Comment 6 bettlerthomas 2006-01-26 17:25:18 UTC 
dup of bug 59598
Comment 7 bettlerthomas 2006-01-26 17:30:46 UTC 
dup of bug 59598
Comment 8 bettlerthomas 2006-01-26 17:32:55 UTC 
dup of bug 59598
Comment 9 bettlerthomas 2006-01-26 17:34:36 UTC 
dup of bug 59598
Comment 10 bettlerthomas 2006-01-26 17:36:19 UTC 
dup of bug 59598
Comment 11 bettlerthomas 2006-01-26 17:37:20 UTC 
dup of bug 59598
Comment 12 lars 2006-01-28 18:43:12 UTC 
duplicate

*** This issue has been marked as a duplicate of 59598 ***
Comment 13 kla 2006-02-06 10:45:30 UTC 
closed as duplicate