brx do more or do less

[maciek]

is there a simple  instruction in do more like there is one in click "copy" single or a pack. it is very useful one

[MikeS]

MOVE will copy one element to another
MOVER (Move Range) will copy a contiguous group of elements
MEMCOPY will copy one or more structures

[BobO]

We added a new COPY box that does many different copy types. No need to use the individual instructions now.

[Controls Guy]

So reading the help it sounds as if COPY is value-aware, is that right?

And if we just want a value-agnostic byte-pipe we should use MEMCOPY?

[BobO]

MEMCOPY has a couple of modes, some of which are type aware. COPY actually is just a pretty face on many underlying instructions. Just use COPY unless there is a good reason not to.

[Controls Guy]

Still confused.  How do you get COPY to do type-agnostic, for example if you're moving a value from MHR to string?  Cast the input to byte level?

So I was asking if we still need MEMCOPY for type-agnostic.

[franji1]

Still confused.  How do you get COPY to do type-agnostic, for example if you're moving a value from MHR to string?  Cast the input to byte level?

So I was asking if we still need MEMCOPY for type-agnostic.

COPY does the "normal" 99% data copying needs (it's just a macro for all the various other instructions).  There is 1% it does NOT do, e.g. MHR to/from STRING is part of that 1%.

There is a chart in Designer 2.2 that shows all the nasty details of all the data copying instructions vs. what they can do.  Look at Help Topic DmD0431 "Data Operations".  99% of the time, COPY will do what you want.

[Controls Guy]

COPY does the "normal" 99% data copying needs (it's just a macro for all the various other instructions).  There is 1% it does NOT do, e.g. MHR to/from STRING is part of that 1%.

There is a chart in Designer 2.2 that shows all the nasty details of all the data copying instructions vs. what they can do.  Look at Help Topic DmD0431 "Data Operations".  99% of the time, COPY will do what you want.

OK, that's a good overview of what COPY is meant for.  I will take a look at that topic.

[BobO]

Still confused.  How do you get COPY to do type-agnostic, for example if you're moving a value from MHR to string?  Cast the input to byte level?

So I was asking if we still need MEMCOPY for type-agnostic.

STRGETB and STRPUTB are safer.