Issue 33909 - crash when ungroup a control group after D&D
Summary: crash when ungroup a control group after D&D
Status: CLOSED FIXED
Alias: None
Product: xml
Classification: Code
Component: code (show other issues)
Version: current
Hardware: All All
: P2 Trivial (vote)
Target Milestone: OOo 2.0
Assignee: marc.neumann
QA Contact: issues@xml
URL:
Keywords:
: 35539 36209 36547 (view as issue list)
Depends on:
Blocks:
 
Reported: 2004-09-07 10:24 UTC by marc.neumann
Modified: 2004-11-25 08:50 UTC (History)
1 user (show)

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

Attachments
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 marc.neumann 2004-09-07 10:24:10 UTC 
1. open a new xml form
2. open the datanavigator
3. insert a new element to the instance
4. D&D the new element to the document
5. ungroup the control group
==>> crash
Comment 1 openoffice 2004-09-20 12:11:54 UTC 
dvo: Crash occurs in: SwOrderIter::Top(), in the following line:
            (*pObjs)[0]->GetDrawObj()->GetOrdNum();  //Aktualisieren erzwingen!
GetOrdNum() gets called on an invalid object.

I don't know the code; I'll have to wait for OD to comment on this.
Comment 2 openoffice 2004-09-22 12:50:53 UTC 
dvo: If one tries enough, the crash occurs at different locations, and in the
master as well. It has probably nothing to do with the eforms2 enhancements.

Anlysis by OD show: Apparently, the handling of controls is somewhat different
from other objects, which causes them to be inserted into the drawing layer at a
different time. This eventually causes things to be inserted twice (in recursive
calls to connectToLayout(..)) which causes the problem. OD knows a lot more
about this, hence I forward the bug to him.

dvo->od: Please take over.
Comment 3 openoffice 2004-09-22 12:53:21 UTC 
dvo: Uhm, I meant to reassign to od, not jsi. Sorry for any inconvenienve.
Comment 4 Oliver-Rainer Wittmann 2004-09-22 13:09:27 UTC 
Accepted.
Adjust summary, because the defect also occurs on the master
Comment 5 Oliver-Rainer Wittmann 2004-09-22 15:06:47 UTC 
Fixed in cws swqbugfixes08 - changed file:
/sw/source/core/draw/dcontact.cxx, 1.32.4.1
Comment 6 Oliver-Rainer Wittmann 2004-09-22 15:11:15 UTC 
Steps to reproduce the crash on SRC680m54:
* open a new text document
* open the data source browser (F4)
* select table "biblio"
* select a column in the grid view, hold SHIFT and CTRL keys, drag and drop it
into the document
* ungroup the inserted objects
* delete the objects one by one
--> crash on the delete of the last object.
Comment 7 Oliver-Rainer Wittmann 2004-09-23 08:16:26 UTC 
Correction: issue is fixed in cws eforms2
Comment 8 Oliver-Rainer Wittmann 2004-10-18 09:12:21 UTC 
*** Issue 35539 has been marked as a duplicate of this issue. ***
Comment 9 Oliver-Rainer Wittmann 2004-10-27 15:09:41 UTC 
*** Issue 36209 has been marked as a duplicate of this issue. ***
Comment 10 Oliver-Rainer Wittmann 2004-10-27 15:11:42 UTC 
*** Issue 36209 has been marked as a duplicate of this issue. ***
Comment 11 aparan 2004-10-29 06:40:13 UTC 
I am still experiencing the problem [crash on delete of fontwork] in 680m58 ?
Comment 12 openoffice 2004-11-02 14:24:54 UTC 
dvo: reopen for QA.
Comment 13 openoffice 2004-11-02 14:27:42 UTC 
dvo->msc: Please test.

dvo->aparan: The fix hasn't been integrated yet. Integration into the main line
will only happen *after* QA confirms its fixed. So if the fontwork issue is
indeed the same as this, then its not surprising if you still expereince the
problem in m58.
Comment 14 michael.ruess 2004-11-03 09:19:46 UTC 
*** Issue 36547 has been marked as a duplicate of this issue. ***
Comment 15 marc.neumann 2004-11-05 09:38:20 UTC 
Hi,

fixed in cws eforms2

Bye Marc
Comment 16 marc.neumann 2004-11-05 09:38:34 UTC 
Hi,

verified in cws eforms2

Bye Marc
Comment 17 marc.neumann 2004-11-25 08:50:01 UTC 
Hi,

fixed in current developer build -> close.
The current developer build can be found at
http://download.openoffice.org/680/index.html
Feel free to reopen if this issue is not fixed in the developer build.

Bye Marc