I think this RFE is now quite important, because of the major restructuring of DAT export methodology:
what was
myop/mychan
is now
myopmychan
causing a LOT of extra nodes to be added just to - for example - column replace an exported cell with a user supplied one:
As an example of what I often, very often find my self dealing with (occasionally before, lots of times since adopting the new export format - hence my plea for this RFE):
inside a master, I have a COLORS DAT representing possible colors:
font on 1 1 1 1
font off 0 0 0 0
bg on 0 0 0 0
bg off 1 1 1 1
next to it, I have an IN DAT which represents user overrides:
then a MERGE with COLORS and IN - with IN column replacing COLORS (appending unmatched in other cases where the override is allowing the user to add his/her own exports to parms inside a master).
Actually the above example is not quite representative of the multitude of times when I’m dealing with parameters that need to be exported, but it’s a case I just run into (so no directly related to the change in export format, but a good example for my RFE nonetheless).
so to override one of the above I would connect a DAT to the IN:
font off .5 .5 .5 .5
the problem is replacing the right row, right? Of course it can be done joining/merging/resplitting the columns (so that font_off for example can be properly found then resplit into fontoff), but it’s a great pain, a waste of cycles and memory when duplicated hundreds of times.
How about a merge that uses a start and end index and internally merges/splits the cells?
ie. replace columns start_column=0 end_column=1
would work just fine!!!
how about it? Or… is there a way just as efficient to do it?