Opened at 2010-03-01T04:33:16Z
Last modified at 2011-05-27T18:06:31Z
#550 assigned planned
how to handle timeline/sequence deletion
| Reported by: | Ichthyostega | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | 0integration |
| Component: | lumieraSteam | Keywords: | interfaces design session |
| Sub Tickets: | #311, #553, #562, #689 | Parent Tickets: | #77, #306, #499 |
Description (last modified by )
Structural assets are typically created automatically and thus difficult to delete (because they'll get immediately re-created, as long as the referral continues to exist).
- How does this relate to Timelines and Sequences?
- do we need an explicit deletion operation for Sequences? for Timelines?
- what happens if attempting to delete them via the AssetManager?
- what happens when the underlying model elements (BindingMO or root track) are dropped?
Change history (6)
comment:1 by , at 2010-03-03T03:07:57Z
| blocking: | 306, 499, 77 → 77, 306, 499 |
|---|---|
| Status: | new → accepted |
comment:2 by , at 2010-03-03T03:14:06Z
| blockedby: | 311 → 311, 553 |
|---|
comment:3 by , at 2010-03-06T02:09:07Z
| blockedby: | 311, 553 → 311, 553, 562 |
|---|
comment:4 by , at 2010-10-18T02:44:55Z
| blockedby: | 311, 553, 562 → 311, 553, 562, 689 |
|---|
non trivial problem, because I want the session to unwind more or less automatically....
comment:5 by , at 2011-05-27T18:06:31Z
| Description: | modified (diff) |
|---|---|
| Owner: | removed |
| Status: | accepted → assigned |
| Type: | todo → planned |
back to future...
Indeed, at some point we should rework the asset handling to some extent. It would be helpful then to have a better understanding about the session internals; thus it's not really a problem if we postpone that now
comment:6 by , at 2025-12-25T00:00:00Z
| blockedby: | 311, 553, 562, 689 |
|---|---|
| blocking: | 77, 306, 499 |
| Parent Tickets: | → 77, 306, 499 |
| Sub Tickets: | → 311, 553, 562, 689 |
Migration MasterTickets ⟼ Subtickets-plugin
Note:
See TracTickets
for help on using tickets.
See the collected specs in the TiddlyWiki, ModelDependencies.
Actually, not so much the deletion is the concern here, but to ensure proper deregistration from the session. The
unlink()virtual function present on each Asset looks like a good candidate. The actual deletion can then be left to the automated instance handling for assets.