Issue 75600 - loop when executing a Basic/UNO dialog in sample document
Summary: loop when executing a Basic/UNO dialog in sample document
Status: CLOSED DUPLICATE of issue 75563
Alias: None
Product: gsl
Classification: Code
Component: code (show other issues)
Version: 680m206
Hardware: All All
: P3 Trivial (vote)
Target Milestone: OOo 2.3
Assignee: philipp.lohmann
QA Contact: issues@gsl
URL:
Keywords: regression
Depends on:
Blocks:
 
Reported: 2007-03-21 13:49 UTC by Frank Schönheit
Modified: 2007-03-21 14:00 UTC (History)
2 users (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 Frank Schönheit 2007-03-21 13:49:37 UTC 
- open the smoketest document (smoketestoo_native/data/smoketestdoc.sxw,
  or r:\etools\10ertest680.sxw in Hamburg's build environment)
- allow macro execution when being asked
- press the "Options" button in the document
=> OOo loops
Comment 1 Frank Schönheit 2007-03-21 13:54:49 UTC 
fs->pl: here is why I assigned this to you:
The loops is because there is a window (a dialog, that is) whose parent is
*itself*. I.e., somebody calls something like
  pDialog->SetParent( pDialog )
More precise, this call is in toolkit/source/awt/vclxwindows.cxx:2135:
  pDlg->SetParent( pDlg->GetWindow( WINDOW_FRAME ) );
What happens here is that the frame window of the dialog is the dialog itself.

As a consequence, certain code places in VCL simply loop when they iterate
through the parent hierarchy.

I don't know whether this is a VCL problem or a toolkit problem. The toolkit
code is in there for ages, so I assume some VCL behavior has changed.

In general, I'd say that Window::SetParent should not allow to set the window
itself as its own parent, to relieve all callers from this task. Additionally,
it might be worth investigating what changed in VCL or Toolkit ...
Comment 2 Frank Schönheit 2007-03-21 13:55:41 UTC 
Adding regression keyword. This does not happen in 680m205, but in 680m206. Thus
targeting for 2.3.
Comment 3 philipp.lohmann 2007-03-21 13:59:48 UTC 
dulicate to issue 75563

*** This issue has been marked as a duplicate of 75563 ***
Comment 4 philipp.lohmann 2007-03-21 14:00:12 UTC 
closing