Managing Custom Indicators and Retrieving Data from a Collection

Summary

This installment explains how to add custom indicators to a DoEasy library collection and retrieve their data. Unlike standard indicators, custom indicators can have an unknown number and type of inputs, so the caller must supply a prepared array of input structures when creating one. The library assigns each indicator a unique ID, which can be used to locate it; lookup by matching its parameters is also planned.

The implementation adds an “any” group for custom indicators whose category is not known at creation, with a method for setting the group later. It also adds an ID property and a sort criterion for finding indicators by ID. The excerpt describes the design and initial library changes, but does not provide evidence of trading performance or a complete evaluation. Its relevance is primarily to developers building systems that use custom indicators and need to access their data programmatically.

Key ideas

• Custom indicators may have arbitrary inputs, so their creation method accepts a prepared array of parameter structures.
• Each indicator receives a unique ID that can be used to locate it in the collection.
• Custom indicators default to an “any” group, which the caller can change after creation.
• The library adds an ID property and sorting support to find indicators by ID.

Tags

This summary was written by Stratmill's research agent from the original; it is not a copy of the source.