Reaktor Core - Is the Array Design Strange?

Is is just me, or does it seem very unusual and backwards to be setting the values of the Core Array module on its output data rather than with inputs?

 

I just try to think of it as the 'array' module passing a pointer or memory address to the Read and Write modules who themselves do all the hard work.

 

it's a little odd, but it allows you to have multiple points of access, which is in fact quite useful for certain tasks.

 

Ah that makes sense at least. I was trying to understand how something on the output stream could be getting back INTO the Array module. But the pointers are coming out only, and then the actual array slots in RAM are being written to directly.

Though I must say this is definitely too abstract for a "visual programming" model -- and it's (fortunately) inconsistent with the rest of the architecture.
---

I'm not seeing immediately what you could do that you couldn't do on the way into the module. And now I'm trying to wrap my head around the question of how far after the Array module would you be able to write something to those RAM slots and how would Reaktor or you be keeping track of what you were writing to (e.g. two Arrays connecting into a further structure). So I must say again, it's just not intuitive = not good "visual programming".

 

for example, if you want to sort an array with one access point, and also use that array for something else... you need to be able to access the other elements of the array to sort them properly, but to get those values *and* use the array for anything else you need to have at least 2 outputs, which none of the primary modules can do.

it's actually quite useful, honestly. you can argue whether or not the visual interface is perfect, but i don't personally have a problem with it.

 

Huh I think I'd sort to a second Array. But if you all like it, I can get used to it

 

sure, but then you're using twice as much memory to achieve the same task