Issue 16198 - Connectors go haywire when moving objects
Summary: Connectors go haywire when moving objects
Status: CLOSED IRREPRODUCIBLE
Alias: None
Product: Draw
Classification: Application
Component: code (show other issues)
Version: OOo 1.1 Beta2
Hardware: PC Linux, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: wolframgarten
QA Contact: issues@graphics
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-06-29 00:25 UTC by andree
Modified: 2003-09-08 16:52 UTC (History)
1 user (show)

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

Attachments
Archive containing sample drawing and 2 screenshots to illustrate issue (54.79 KB, application/octet-stream)
2003-06-29 00:30 UTC, andree 		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 andree 2003-06-29 00:25:54 UTC 
Sceanrio:
In attached drawing, select all objects (13), then move the lot to a different
place.

Result:
All objects that are not connectors are moved correctly, some connectors are
moved correctly while other loose their connection to the object and point to
arbitrary locations.

Expected Result:
All objects including connectors moved correctly.

Remarks:
Apart from the attached drawing, I also include 2 screenshots to highlight the
issue.
Comment 1 andree 2003-06-29 00:30:50 UTC 
Created attachment 7216 [details]
Archive containing sample drawing and 2 screenshots to illustrate issue
Comment 2 wolframgarten 2003-06-30 07:17:27 UTC 
Duplicate.

*** This issue has been marked as a duplicate of 16197 ***
Comment 3 wolframgarten 2003-06-30 08:11:01 UTC 
Reopened.
Comment 4 wolframgarten 2003-06-30 08:32:58 UTC 
This one is reproduceable in OO 1.1beta2 but not in a current internal
version. The fix will be included in OO 2.0. Thanks for your help.
Comment 5 andree 2003-06-30 12:38:06 UTC 
Huh? It's confirmed in 1.1b2, but it's not in a 'current internal
version' - why would it take until 2.0 to fix it then? I'm puzzled,
please, clarify.

If it is in 1.1b2 but not in a 'current internal version' (whatever
that means) why don't we wait for 1.1rc1 and I restest?

Apart form all this, this bug is not only annoying but IT IS A
REGRESSION FROM 1.0 - sorry for yelling, I just wanted to make the
point. ;-)
Comment 6 wolframgarten 2003-07-01 12:21:32 UTC 
The file with the fix is /svx/source/svdraw/svdmrkv.cxx. If you need
an earlier fix you are free to build you own version with the fixed
file. So have fun. No need for shouting.
Comment 7 wolframgarten 2003-07-01 12:21:54 UTC 
Closed AGAIN.