The following table summarizes the known issues and limitations of the igBulletGraph control. Detailed explanations of known issues and the possible workarounds are provided for some of the issues in the following summary table.
 |
Workaround available |
 |
No known workaround |
 |
Fix planned |
| Issue | Description | Status |
|---|---|---|
| Only one performance bar and one comparative marker supported | The igBulletGraph control supports only one performance bar and one comparative marker. |
|
| No label collisions detection | The igBulletGraph control does not provide means for detecting label collisions. As a result, when the space to visualize the labels is not sufficient, label collisions may occur. |
|
| Performance bar can be drawn only from the minimum scale position | The starting position of the performance bar can only be at the minimum value of the scale, i.e. the performance bar cannot originate from an arbitrary position. | |
The igBulletGraph control supports only one performance bar and one comparative marker.
Workaround
The effect of displaying multiple performance bars or multiple comparative markers can be achieved by overlaying several instances of the control.
The igBulletGraph control does not provide means for detecting label collisions. As a result, when the space to visualize the labels is not sufficient, label collisions may occur.
Workaround
Make sure that in the container of the control there is sufficient space to display the labels properly.
View on GitHub