The base class for all kinds of tools used in technical analysis, such as trendlines, channels, fibonacci retracements etc.
All tools are represented by a set of "handles", which are basically 2d points that can be manipulated by the user to change the shape of the respective tool. Additionally, in addition to the common configuration options, tools can offer a set of so called "actions" for common tasks that offer shortcuts for often used features - these could for example be used to populate a context menu.
will be called before methods are called that need to access x/y-coordinates can be overriden to set up the cache values needed in the other methods The meta parameter passed to the method includes a reason for the redraw, and potentially the indices of the updated values
called after each deserialization all handles have already been configured at this point or interactive placement has been started default implementation of this method applies all options via set
must 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 BG.charts.Object:get instead
Optional
readWriteOnly: booleandefault: true
Optional
modifiedOnly: booleandefault: true
Optional
nonEphemeralOnly: booleandefault: true
by implementing this methods tools can request a special mouse cursor
to use in combination with custom event handling (e.g. for different actions such as buttons)
the selection logic itself has to be implemented based on the values passed to handleEvents
which is always called with the most recent values before this method
desired cursor (all standard css cursors are supported) or null for default
returns the categorization of the objects options can be used for displaying a more structured user interface
by implementing this methods tools can control the picker markers on the X- and Y-Axes that are shown when interacting with the tool should only be used in combination with custom event handling tools that are controlled via handles should not overwrite this method and stick to the default behaviour
desired picker dimensions
returns the style object
return a BG.locale.Translator instance
handle events
the original mouse or touch event
the event to be handled
Optional
button: numberthe pressed button
Optional
layerX: numberthe x-coordinate
Optional
layerY: numberthe y-coordinate
Optional
hovered: booleantool is hovered
Optional
editable: booleantool is currently editable
boolean indicating wether the event has been handled
checks if the tool is (at least partly) visible in the current viewport range always return false if tool has not been assigned to a chart yet or if it has no valid bounds
Note: This method does NOT account for value of the "visible" option; e.g. if visible is set to false, but the tool WOULD be visible in the current viewport range, this method returns true!
move the specified handle to a new position
the index of the handle to be moved
the new index (x-coordinate) of the handle
the new value (y-coordinate) of the handle
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
Method that allows reading of values in an instance-specific cache Can be used to reduce the amount of necessary calculations (e.g. x/y-coordinates) by storing/retrieving them only when necessary Keys and values need to be defined in a type that will be passed to the parent BG.charts.Tool class
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
Programatically change the layout of the tool.
Handles are specified as an array of numbers, either in the format [timestamp, value], or [timestamp, offset, value]. The number and layout constraints of handles depends on the type of the tool being added. See the documentation of the respective tool class for detailed information.
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.
Helper method, must not be called directly Used for validating if a specified chart is suitable for placement of this tool instance
e.g. charts that require a reference OHLC input can check if one is available, and if it uses the correct aggregation, etc.
Helper method, must not be called directly. Used for validating new layouts provided to BG.charts.Tools.setHandles method
When implementing a custom tool, you can overwrite this function to validate specific constraints
This method is explicitly allowed to change options depending on provided layout.
when 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[]Method that allows storing of values in an instance-specific cache Can be used to reduce the amount of necessary calculations (e.g. x/y-coordinates) by storing/retrieving them only when necessary Keys and values need to be defined in a type that will be passed to the parent BG.charts.Tool class
Static
getMethod for plugins to describe which other plugins they want to replace
Static
guardStatic
listenerStatic
set
*Example of an options definition with the most common attributes: