Anonymous | Login | 03-01-2021 19:47 UTC |
Main | My View | View Issues | Change Log | Docs |
Viewing Issue Simple Details [ Jump to Notes ] | [ View Advanced ] [ Issue History ] [ Print ] | |||||||||||
ID | Category | Severity | Reproducibility | Date Submitted | Last Update | |||||||
0005404 | [Croquet] Hedgehog | minor | always | 11-12-06 23:17 | 11-12-06 23:17 | |||||||
Reporter | howardstearns | View Status | public | |||||||||
Assigned To | ||||||||||||
Priority | normal | Resolution | open | |||||||||
Status | new | |||||||||||
Summary | 0005404: #destroy protocol | |||||||||||
Description |
What is the protocol for #destroy? This was hard to make useful in Jasmine because we wanted to support having the same instance appear in multiple places in the scene graph. Hedgehog doesn't allow this, so we ought to be able to make #destroy be useful. It's becoming imporant for embedded apps and media. Consider the case of a series of embedded apps or video/microphone objects which tie up various resources outside the island. Now consider deleting a composite object that has leaves which are these objects, or which are TWindows with these objects as contents. |
|||||||||||
Additional Information |
What I have in mind is: TFrame>>destroy self frameChildrenDo: [:child | child destroy]. "<= This line is new" frameParent ifNotNil:[frameParent removeChild: self]. TWindow>>destroy super destroy. contents ifNotNil: [contents destroy]. "<= This line is new" Or maybe this should be broken into separate #preDestroy, #destroyMe, #postDestroy methods for more control in customization. |
|||||||||||
Attached Files | ||||||||||||
|
![]() |
|||||||||||
|
There are no notes attached to this issue. |
![]() |
|||
Date Modified | Username | Field | Change |
11-12-06 23:17 | howardstearns | New Issue | |
11-12-06 23:27 | howardstearns | Relationship added | parent of 0005405 |
Mantis 1.0.8[^]
Copyright © 2000 - 2007 Mantis Group
32 total queries executed. 26 unique queries executed. |