Ticket #550 (assigned planned)

Opened 2 years ago

Last modified 9 months ago

how to handle timeline/sequence deletion

Reported by: ichthyo Owned by:
Priority: normal Milestone: 0integration
Component: lumieraProc Keywords: interfaces design session
Cc: Blocked By: #311, #553, #562, #689
Blocking: #77, #306, #499

Description (last modified by ichthyo) (diff)

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

comment:1 Changed 2 years ago by ichthyo

  • Status changed from new to accepted
  • Blocking

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.

comment:2 Changed 2 years ago by ichthyo

  • Blocked By 553 added

comment:3 Changed 2 years ago by ichthyo

  • Blocked By 562 added

comment:4 Changed 16 months ago by ichthyo

  • Blocked By 689 added

non trivial problem, because I want the session to unwind more or less automatically....

comment:5 Changed 9 months ago by ichthyo

  • Owner ichthyo deleted
  • Status changed from accepted to assigned
  • Type changed from todo to planned
  • Description modified (diff)

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

Note: See TracTickets for help on using tickets.