You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Crosshair is a service component as well as tooltip, legend around composite-y.
I can distinguish two approaches:
Currently tooltip renders itself into separate container outside the chart on special event thrown out of the chart. This is done via overlaying svg compositeY container with exact coordinates prepared specifically for tooltip in the chart. That is a consistent way to implement crosshair as well.
While legend can be rendered in its own container outside the chart, tooltip and crosshair should better reside within svg along with chart drawings. Same as Line, Bar and other drawings are. In this case crosshair would be able to listen to svg mouse events on its own.
But Line and Bar are implemented as subviews of CompositeY which is not a true component approach too.
So, in order to implement Crosshair as a component it should accept svg as container, listen to its mouse events and have a reference to parent config model (compositeY.config) as new implementation of legend and colorPicker does (see htmlcontainer branch). By this reference crosshair would be able to retrieve right data (from own reference to dataModel) and format it for rendering (timestamp).
The text was updated successfully, but these errors were encountered:
Crosshair is a service component as well as tooltip, legend around composite-y.
I can distinguish two approaches:
Currently tooltip renders itself into separate container outside the chart on special event thrown out of the chart. This is done via overlaying svg compositeY container with exact coordinates prepared specifically for tooltip in the chart. That is a consistent way to implement crosshair as well.
While legend can be rendered in its own container outside the chart, tooltip and crosshair should better reside within svg along with chart drawings. Same as Line, Bar and other drawings are. In this case crosshair would be able to listen to svg mouse events on its own.
But Line and Bar are implemented as subviews of CompositeY which is not a true component approach too.
So, in order to implement Crosshair as a component it should accept svg as container, listen to its mouse events and have a reference to parent config model (compositeY.config) as new implementation of legend and colorPicker does (see htmlcontainer branch). By this reference crosshair would be able to retrieve right data (from own reference to dataModel) and format it for rendering (timestamp).
The text was updated successfully, but these errors were encountered: