Issue 30671 - Frame::dispose() leads to some repaint errors within the last active frame
Summary: Frame::dispose() leads to some repaint errors within the last active frame
Status: ACCEPTED
Alias: None
Product: App Dev
Classification: Unclassified
Component: api (show other issues)
Version: 3.3.0 or older (OOo)
Hardware: All All
: P3 Trivial
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-06-24 09:53 UTC by andreas.schluens
Modified: 2013-07-30 02:37 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 andreas.schluens 2004-06-24 09:53:14 UTC 
If we try to dispose a new loaded frame immediatly after creation, the last
active frame (which should not related to the new frame anyway!) will show some
repaint errors. E.g. all scroll bars and all buttons of combo boxes inside the
toolbars wont be painted right. Refreshing of the window (minimize/maximize)
doesnt help.
Comment 1 andreas.schluens 2004-06-24 10:00:41 UTC 
This behaviour isnt reproducable with basic ... but with an API test. So it
seems to be related to "concurrent access" to shared structures or may be
related to an focus dependend informations (e.g. CurrentViewFrame) ...

Please run "%SOLARENV%\bin\checkapi -o
fwk.Frame::com::sun::star::lang::XComponent" to reproduce it.
Comment 2 Rob Weir 2013-07-30 02:37:22 UTC 
Reset assignee on issues not touched by assignee in more than 1000 days.