4.1.5 / 4.1.6 - Crash when attempting to Undo a pasted effect

[gerry]

I'll look into the crash but regarding the copy and paste alignment I can see there are some misconceptions on how it works right now in xLight versus how you think it works.  Remember that we work as a grid and non-grid based editor so when you drag a group of cells to select the effects it does not matter how many cells above the effect you started on in regards to where the paste will happen.  The start point is defined by the location of the first selected effect.  When you click a target location you are defining where you want that first effect to be located.  Remember you don't even need a grid to copy or paste.  I had to design it where you could copy with the grid off and paste with the grid on and vice versa.

Hi,
I thought that this was exactly what I did and showed in the screen prints
The start location (as highlighted) is one cell above the effect (ie blue /white on cell).
The target location  (as highlighted) is exactly the same place - two rows over. But the result is skewed.
It looks (to me ) that when the copy is done that the 'empty' cell that I highlighted is not used as a start , but the start is taken as the nearest cell that is populated (ie in this example one cell down).
*** It could be because this is being done at the node level ***
Same thing for the singing faces (custom effect) copy and paste that I posted about above yesterday (also at "node" level) . My work around is to populate the cell that I am going to copy from (ie ensure that it is not blank), copy and paste and then delete the unwanted cell.

In this example , if I highlight the area starting from the blue cell, I cant easily 'grab' and paste a bunch of cells - it seems to mostly grab and paste one cell only - hence why I start one cell above.

   
 

[Gilrock]

That's exactly what I was trying to describe.  The empty cells don't count.  When you click the destination you are selecting where the first selected effect is going to land...not where the first selected cell is going to land.  Selection using the grid is just a means of grabbing the effects...once you select the effects it does not matter which cells were highlighted to select them reason being that you can control select additional cells and you can turn off the grid and add more effects to the selection.  So the selection has nothing to do with the cells.

[gerry]

Hi Gil,

I am beginning to understand ....(sorry that it has taken this long ).

you are right - this is not the same as what we are currently used to in copying and pasting stuff from Excel , Word tables , LSP , where one selects the content of the grid that is highlighted.

So accordingly, I will adjust my thinking when pasting...

What should happen in the scenario where you have effects at a node level , but when collapsed nothing can be seen at the model level. If you copy at the model level (when collapsed) and paste (when collapsed), should it copy all the underlying node data ?

In my example, that you had today (with the blue and white squares), if you copied 4 secs at the model level and pasted it (at the model level) 10 secs away - should the entire underlying check effects be copied and pasted ?

I can send some screen shots if my question is not clear.


 

[Gilrock]

We only copy what is on visible rows.

[Gilrock]

I checked in some changes last night that appear to fix the crashing when doing an Undo on Strand or Node layers.  So you'll have to wait for the next release to try it out.

[gerry]

I checked in some changes last night that appear to fix the crashing when doing an Undo on Strand or Node layers.  So you'll have to wait for the next release to try it out.

Thank you Gil,

I had previously posted (about 3-4 versions ago)  a couple of other issues ** when working at the node level ** that also caused crashes before an Undo - eg highlight a range of cells (downwards) and use the on/ramp down key etc.

I'll have a look later today to see if they still exist in case they are related