column handling confusion?

[Zoltán]

hi,
i am a bit confused about handling columns.

1. there was a project where I had a full deck, and was working on another.
I removed a column, and the other deck has lost the clips and column. maybe I did not read the manual carefully enough, but that was suprising.

2. Also the column assigned mappings get messed up (?) when inserting/removing columns.
when i insert a column on a deck before one with mapping assigned, the mapping follows the columns after the insert position, the contents are pushed to the right as one would expect, but only on that single deck.
In other decks, the mapping follow the insertion, but the content does not move!

I think assigned column mappings should follow the content when inserting /removing columns. but if the logic is as I see now: there is a composition, which has columns, and there are decks which can use those columns globally. - then all other deck's columns should follow the insertion.

You all know Excel where there are tabs for spreadsheets with columns, and an operation on one tab does not affect other tabs.
The Excel way Resolume would be as a composition which has decks where every deck has its columns, even with different column count. This would be my way of logic.

In another topic was a feature request dragging columns to rearrange, whis has a +1 from me, but
how would that mess with the above described?

I would like some input on this, do I see it right how resolume behaves?

[Joris]

Thanks for your feedback.

1. This should not happen. I tried to recreate this, but in all cases, only the content in the current deck is removed. All other content in other decks remains intact. Can you recreate this with a particular set of actions?

2. I assume you are using Composition Midi Map? We recommend using Application Midi Map, because here the behaviour is consistent: when a column is inserted, a mapping will stay tied to the column, regardless if the content moves or not.

In Composition Midi Map this behaviour can be confusing, because the mapping moves in other decks, but the content does not. This is done to keep consistency with the mapping assignments, without changes being made to the structure of decks you cannot see.

I hope that explains things a bit.

[Zoltán]

1. I could not recreate this, it was 3-4 months ago (on an older release?).
It could be that I don't remember correctly, but column was removed from the other deck thats sure, I thought it had clips in it but I'm not so sure now about this part, sorry.
It was in middle of a very busy day, so I didn't have time to look into it further, but I did not delete any columns since!

2. I was using composition key map to launch columns. About an other thing I had using this i have posted a feature request here : viewtopic.php?f=6&t=11068

Thanks for the clarification!