Cut Sequence

[ouadji]

for the code around the sequence, an growth of the code like "add frame"

[fabric]

Wait... what is being suggested here?

ouadji: Do you intend to split the frames permanently, or do you intend that an "invisible wire" remains between the "1" and the "add" input?!

[dthor]

Judging by his picture, it looks like the Idea is to split frames permanently - notice that the wire going to the Multiply node is now broken.

I think that this Idea would make code refactoring less of a pain.

[fabric]

@dthor: That's what I assumed too, but X's post offers an alternate interpretation...

[ouadji]

@fabric :

ouadji : Do you intend to split the frames permanently : yes!

or do you intend that an "invisible wire" remains between the "1" and the "add" input?!

no, nothing to do with my proposal.

[X.]

That's what I understood too, hence my perfectly ironical suggestion. My only point is, you are starting to put things in a sequence, and then decide to break/split the sequence. Naturally, as a future/ex- not employee of NI, I am worried that you will next ask to fuse two sequences together...

[JKSH]

---

@X. wrote:

My only point is, you are starting to put things in a sequence, and then decide to break/split the sequence. Naturally... I am worried that you will next ask to fuse two sequences together.

---

I couldn't figure out what you're trying to say, sorry... What's the issue here? (Or do I need to upgrade my sense of humour? :P)

[ouadji]

"Naturally... I am worried that you will next ask to fuse two sequences together."

No, don't be afraid, I have no intention to ask to merge sequences.

[Intaris]

I am worried that you will next ask to fuse two sequences together...

Why? Why would that be such a terrible thing.  I really think some advances in handling multi-frame structures within the IDE (And I mean ALL multi-frame structures) is long overdue.

Want to merge two event structures into one?  OK.  You have 30+ frames of different user events in each structure?  Cancel your plans for the rest of the day....

Changes like this are sometimes neccessary on the architecture level when making significant changes to the workings of a program.  From a workflow point of view, I fail to see why in this day and age such operations must be so tedious.