On Sun, Mar 30, 2008 at 2:51 AM, Matthew Allum <[EMAIL PROTECTED]> wrote: > > The X11 backend is not cleaning up properly as yet when an extra stage > is closed but its not crashing (but is emitting warnings). It shouldn't > be anything that major, I'll take a look asap if you dont beat me to it.
OK, attached patches should fix the immediate issues I've found. Destroying the stage raises an interesting issue regarding memory management, I think. How should the lifecycle of behaviours and timelines be managed in such a case? The very least behaviours should notice when actors get destroyed and stop updating them, but it could be convenient to be able to 'attach' a timeline/behaviour to actor(s) so that when all actors are gone, so would the timeline. Quite similar to floating references and containers, but in reverse. Thoughts? -- Tommi Komulainen [EMAIL PROTECTED]
0001-OSX-add-multistage-support.patch
Description: Binary data
0002-OSX-handle-gracefully-NULL-title.patch
Description: Binary data
0003-test-multistage-stop-and-destroy-the-timeline-when.patch
Description: Binary data
0004-ClutterActor-ensure-state-reversal.patch
Description: Binary data
0005-ClutterStage-cancel-redraw-idle-on-hide.patch
Description: Binary data
