Issue 102812 - Connectors in existing Draw document take a huge detour in OOo version 3.1.0
Summary: Connectors in existing Draw document take a huge detour in OOo version 3.1.0
Status: CONFIRMED
Alias: None
Product: Draw
Classification: Application
Component: open-import (show other issues)
Version: OOo 3.1
Hardware: Unknown All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-06-15 20:26 UTC by stephan66
Modified: 2013-08-07 15:40 UTC (History)
2 users (show)

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


Attachments
Draw version 3.0.0 correctly displaying the connectors in a diagram (138.33 KB, image/png)
2009-06-15 20:27 UTC, stephan66
no flags Details
Draw version 3.0.0 incorrectly displaying the connectors in a diagram (182.92 KB, image/png)
2009-06-15 20:28 UTC, stephan66
no flags Details
Document with incorrect connectors marked red (saved/edited in OOo 3.1.0) (13.83 KB, application/vnd.sun.xml.draw)
2009-06-15 20:37 UTC, stephan66
no flags Details
Draw document edited/saved with OOo 2.4.0 (14.09 KB, application/vnd.sun.xml.draw)
2009-06-16 09:04 UTC, stephan66
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description stephan66 2009-06-15 20:26:33 UTC
An existing Draw document (previously edited with version 2.4) contains
connectors: arrows and lines connecting rectangles. In all versions of Draw up
to now (tested with Open Office 3.0.0 as supplied with openSuSE 11.1) the
document is displayed correctly.

When opening this document in version 3.1.0 several connectors take huge detours
between their start and end points. Tried on:
openSuSE 10.3 (OOO310m21, build 9319, Novell build 3.1.0.6)
openSuSE 11.0 with wine 1.22 (OOO310m11, build 9399, Novell build 2009=05-27)
Windows XP SP3 (OOO310m11, build 9399)
Comment 1 stephan66 2009-06-15 20:27:46 UTC
Created attachment 63010 [details]
Draw version 3.0.0 correctly displaying the connectors in a diagram
Comment 2 stephan66 2009-06-15 20:28:41 UTC
Created attachment 63011 [details]
Draw version 3.0.0 incorrectly displaying the connectors in a diagram
Comment 3 stephan66 2009-06-15 20:37:12 UTC
Created attachment 63012 [details]
Document with incorrect connectors marked red (saved/edited in OOo 3.1.0)
Comment 4 wolframgarten 2009-06-16 07:53:25 UTC
Please attach a version of the document that is not saved in 3.1 so I can see
how it looks when loaded in 3.0.
Comment 5 stephan66 2009-06-16 09:04:20 UTC
Created attachment 63019 [details]
Draw document edited/saved with OOo 2.4.0
Comment 6 stephan66 2009-06-16 09:12:54 UTC
Just uploaded the Draw document edited and saved with OOo 2.4.0.

For the correct connector placement see screenshot in first attachment:
OpenSuSE 11.1 OOo 3.0.0 anoniem.png

For the incorrect connector placement see screenshot in second attachement:
OpenSuSE 10.3 OOo 3.1.0 anoniem.png

Some additional observations that might help:

- saving this document in version 3.0.0 as either odf 1.1 or odf 1.2 makes the
connector problem disappear in version 3.1.0. 
- after saving this document in version 2.4.0 (odf 1.1) the connector problem
still exists in version 3.1.0.

It seems version 3.1.0 is in some way incompatible with connectors in odg
documents created with version 2.4.

Happy bug hunting!
Comment 7 wolframgarten 2009-06-16 09:47:05 UTC
Reproducible. Reassigned.
Comment 8 clippka 2009-06-16 09:55:56 UTC
reassigned, retargeted because it is a regression
Comment 9 Armin Le Grand 2009-07-30 17:37:09 UTC
AW->SJ: Compared between SO8 and DEV300 m52 version. When tabbing through the
document, the first connector (left side) is connected to the wrong GluePoint on
the left object. Even more intersting is the 2nd connector: It's added to the
same GluePoints at the same objects, but the three control values are
interpreted somehow way different. 

StarOffice8: only the first is used (on value 0.0, use context menu to open
Connector dialog).

DEV300 m52: all three values are 'active' (not grayed out; they are all 0.0, but
internally they seem to have another value).

I guess Your changes to take out the item/local value buffering caused this.
Please have a look.
Comment 10 sven.jacobi 2009-09-28 11:29:13 UTC
changed target