This works. In the main net, not in a macro:
Pick -> Extract("positions")->List(input 1)->Print("rd")
Simultaneously, GetGlobal->List(input 0) and GetGlobal(link)->SetGlobal(link)
Simultaneously, Link->SetGlobal(object)Execute on Change and start clicking. Watch the Message Window.Forget about appending to a file, just overwrite it each time with the new longer list.
The concept of "Global" is that state is retained between executions, so don't use it inside a macro until you understand how this violates the data flow concept. Use the "Local" variants inside macros. However, since state is not retained in Local's in macros, you can't accumulate a list with outputs from outside. Thus your dilemma (until now).
Tobias: in over 10 years of using DX almost every day on hundreds of diverse projects, I've needed to write exactly 5 modules. Beginners should instead spend their time grasping the data model (they'd need to do that to write a module anyway), then exploring the depth of the Structuring category. Saves a lot of time. Modules are needed for some intensely complex calculations and device drivers, but almost everything else is better solved in the UI: more maintainable and distributable. Most people that have slaved over C code or MatLab scripts or whatever are totally stunned by what one of us DX weenies can accomplish in 10 minutes with standard modules. (:-)
Chris Pelkie Vice President/Scientific Visualization Producer Conceptual Reality Presentations, Inc. 30 West Meadow Drive Ithaca, NY 14850 [EMAIL PROTECTED]
