Search the Community
Showing results for tags 'interfaces'.
I had some time to learn about new interfaces and finally I could implement my collection class as I had envisioned. I didn’t want to use iterable and iterator names, because I thought that would have been too bold a claim. The original version of the collection class was (and is) used as a collection of sequence steps. Each element can be either a sequence command (send message, wait timer, wait complete etc.) or another collection of commands (sub-sequence). That’s the reasons for the labels and search method. Otherwise it is just a fancy (Rube Goldberg) array. Next method is recursive and it steps through all elements in the collection. Execute is only method, which requires override. For now, it’s at least an exercise in new interfaces. I don’t know if it’s useful enough to be in the code repository, but I can polish it up if needed. -- Marko H Certified LabVIEW Architect www.optofidelity.com Iterable Collection LV2020.zip