Feature/expand object arrays #121
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This makes it much simpler to define XTS objects in user-code and have the mediator be able to register them via Mediator.Add... methods.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This separates the number of XTS objects (Stations, Zones, etc) that are created on FB_XTS from the actual number of elements in the arrays within Mediator. This streamlines the end user's code to be able to add arbitrary XTS objects in code and register them with the mediator without stepping outside the array.
The Mediator arrays will detect if more objects are added to them than there are spaces available via a warning message with suggested resolution. Documentation for GVL.Params has been added. Example code for creating an arbitrary XTS object inside an FB is also included.