Opened at 2010-07-13T02:04:41Z

Closed at 2010-09-25T02:01:06Z

#647 closed todo (done)

decide implementation technique for global pipes

Reported by: Ichthyostega Owned by: Ichthyostega
Priority: grave Milestone: 0integration
Component: lumieraSteam Keywords: design session
Sub Tickets: Parent Tickets: #312, #442, #648, #651, #652, #657, #658, #659

Description

unresolved problem which blocks several further related topics

  • Model-A: use kind-of a placeholder MObject per pipe, attached by placement
  • Model-B: don't represent them 1:1 in the model, just attach any effects to the Binding (corresponding to the timeline)

Change history (9)

comment:1 by Ichthyostega, at 2010-07-13T02:17:21Z

blocking: 442 → 442, 648

comment:2 by Ichthyostega, at 2010-07-17T23:24:02Z

blocking: 442, 648 → 442, 648, 312
Status: new → accepted

mulled that over the last weeks. I'm more and more geared towards introducing dedicated Bus MObjects to serve as attachment point

comment:3 by Ichthyostega, at 2010-07-17T23:45:24Z

blocking: 442, 648, 312 → 312, 442, 648, 651

comment:4 by Ichthyostega, at 2010-07-17T23:49:45Z

blocking: 312, 442, 648, 651 → 312, 442, 648, 651, 652

comment:5 by Ichthyostega, at 2010-09-25T01:57:33Z

blocking: 312, 442, 648, 651, 652 → 312, 442, 648, 651, 652, 657

comment:6 by Ichthyostega, at 2010-09-25T02:01:06Z

Resolution: → done
Status: accepted → closed

Decided to go for a dedicated object (Model-A)

comment:7 by Ichthyostega, at 2010-09-25T02:11:51Z

blocking: 312, 442, 648, 651, 652, 657 → 312, 442, 648, 651, 652, 657, 658

comment:8 by Ichthyostega, at 2010-09-25T02:19:14Z

blocking: 312, 442, 648, 651, 652, 657, 658 → 312, 442, 648, 651, 652, 657, 658, 659

comment:9 by Undercover Agent, at 2025-12-25T00:00:00Z

blocking: 312, 442, 648, 651, 652, 657, 658, 659
Parent Tickets: → 312, 442, 648, 651, 652, 657, 658, 659

Migration MasterTickets ⟼ Subtickets-plugin

Note: See TracTickets for help on using tickets.