Optional
Readonly
eventsemits alert id of the alert which is to be changed, and the new value and comment
emits alert which is to be deleted
triggered by the manageAlerts button, which should open the alerts list
emits when a new alert should be created
triggered by the 'inda' button, which should open the indicator alerts list
Optional
optionProtected
optionsStatic
optionsreturns or sets the attribute of an option this function should be used with care - modifications of internal properties might break stuff!
Optional
v: anymust be called after willUpdateOptions
once all actions that might potentially changed values of any options are done
IMPORTANT: methods must be called in balance; e.g. for each call to willUpdateOptions
, you must call didUpdateOptions
exactly once.
returns a flat representation of all available config options in the form of a key-value-object optionally only values that are not read-only can be returned
IMPORTANT: this method will always convert I18NStrings to strings, so for displaying strings in a UI use individual calls to Object:get instead
Optional
readWriteOnly: booleandefault: true
Optional
modifiedOnly: booleandefault: true
Optional
nonEphemeralOnly: booleandefault: true
returns the value of the requested option, or a list of all available config options if no parameter is specified.
Optional
s: stringOptional
flags: numberreturns the currency of the chart Can be used by clients to determine which alerts to display or to correctly calculate the value of the alert when using an exchange rate
returns the data object
returns the exchangeId of the chart Can be used by clients to determine which alerts to display
returns the categorization of the objects options can be used for displaying a more structured user interface
returns the input object
returns the used inputs
returns the instrumentId of the chart Can be used by clients to determine which alerts to display
Creates list of legend entry chunks to be displayed in the legend for the index pickerIndex
returns the precision of the chart. Can be used by clients to determine how many decimals are needed
returns the objects current state
return a Translator instance
Automatically toggles the EXPOSED flag on dependent options when a 'parent' option changes value.
For each entry in optionDependencies
, whenever the parent option
emits an optionChanged
event, its dependents (listed in dependentNames
)
will be exposed (flag added) if the new value === exposeWhen
, or
hidden (flag removed) otherwise.
Map where:
exposeWhen
: the boolean that triggers exposing the dependents or a function with the newValue for custom validationdependentNames
: array of dependent option names whose EXPOSED flag will be toggledclass Test extends ChartbreakerObject {
constructor() {
super();
this.registerOptionDependencyVisibility(new Map([
['showLine', { exposeWhen: true, dependentNames: ['lineColor', 'lineStyle'] }],
['advancedMode', { exposeWhen: false, dependentNames: ['simpleModeOnlyOption'] }],
['description'], { exposeWhen: (text) => !!text.length, ['fontSize', 'fontColor']}
]));
}
}
life cycle method; called when the object should stop normal operation if objects have any pending subscriptions/requests, they should all be stopped here
the object is also responsible for clearing the loading flag from it's state if it is currently active failing to do so will trigger a fatal error
object might be started again afterwards (start) or destroyed (destroy) this is not known yet at this point
called after start or restart
can be called to tell the object that it should recover from an error and resume will have no effect if no retryable error is currently associated with the object
Optional
type: TypeMethod to be optionally called when the ToolGenerator is no longer in use and should be removed from the chart, e.g. if all the managed tools have been removed by the user or if the generator has become irrelevant. This method will have no effect if the generator is still managing tools. As such, they should first be removed before calling this method.
The return value indicates if the self-destruction was successful.
Not serializing any of the options, not even the underlying ones from Object
will set validate and then set the specified option(s) to the provided value(s) after validation
NOTE: if multiple options are used, will return false if at least one value is not valid values are applied individually however, so one option might be set even if the value for another is invalid
Optional
v: anyOptional
flags: ObjectEFlagsadds an alert to the generator and displays it in the chart at the position of the value.
method for clients to set multiple alerts at once
by default EventEmitters will print a warning if more than 10 listeners are added for a particular event. This is a useful default which helps finding memory leaks. Obviously not all Emitters should be limited to 10. This function allows that limit to be increased. Set to zero for unlimited.
set number of usable inputs; must be at least 1 calling this method resets previously required buffers
the optional second parameter can be used to provide name(s) for the input option(s) Note: number of provided names needs to be identical to requested number of inputs
Optional
names: string | string[]Sets the objName and objType of the Object reverts to the default ones if no arguments are given
Optional
objType: stringOptional
objName: stringReturns a string representation of an object.
will set validate value(s) for the specified option(s)
NOTE: if multiple options are used, will return false if at least one value is not valid
Optional
v: anyOptional
flags: ObjectEFlagswhen using custom getters/setters (via _get/_set) in options, the values of options can change
without .set being called - or there might not even be a setter for readonly options;
for example, if the getter simply returns the value of a member variable
this variable could be modified directly.
In this case, events such as optionChanged
would not be fired, and listeners would not be informed about the change.
To account for such cases, the methods willUpdateOptions
and didUpdateOptions
should be called directly BEFORE and AFTER
actions that might potentially change values of options.
the correct events will then automatically be triggered when calling didUpdateOptions
.
if the options that could change are known, they can be supplied via the optional parameter. This provides a small performance gain in most situations.
IMPORTANT: methods must be called in balance; e.g. for each call to willUpdateOptions
, you must call didUpdateOptions
exactly once.
Optional
options: string | string[]Static
getMethod for plugins to describe which other plugins they want to replace
Static
guardStatic
listenerStatic
setStatic
visualizeEnable/disable visualizing the validity of alerts globally
Dynamically place AlertTools in the chart