Pie chart API reference
- Example
- Properties
- Methods
- The Horseshoe meter
- The Segmented donut
- The Activity meter
- The RadialProgress meter
- The coordinates properties
- Events
- Effects
Example
<script> labels = ['Fred','Rich','John','Paul','Jason','Hoolio','Kevin']; new RGraph.Pie({ id: 'cvs', data: [564,155,499,611,322,568,389], options: { marginLeft: 100, marginRight: 100, tooltips: '<b>Results:</b><br />%{key}', tooltipsFormattedKeyLabels: labels, labels: labels, linewidth: 2, colorsStroke: 'white', shadow: false, tooltipsCss: { fontSize: '16pt', textAlign: 'left' }, exploded: [25] } }).draw(); </script>
Properties
You can use these properties to control how the chart appears. You can set them by including them in the options section of the configuration as shown above.
obj.set('name', 'value');
- Chart configuration properties
- Margin properties
- Color properties
- Labels and text properties
- Title properties
- Shadow properties
- Interactive features properties
- Key properties
- Miscellaneous properties
Chart configuration properties
Pie chart
using this instead of the margins. As well as a number, that gives the exact coordinate of the center position of the chart, this can also be a string
like this: centerx: '+25'
or this: centerx: '-40'
which is then used to adjust the calculated coordinate.Pie chart
using this instead of the margins. As well as a number, that gives the exact coordinate of the center position of the chart, this can also be a string
like this: centery: '+25'
or this: centery: '-40'
which is then used to adjust the calculated coordinate.Pie chart
using this instead of the margins. As well as a number, that gives the exact size of the chart, this can also be a string
like this: radius: '+25'
or this: radius: '-40'
which is then used to adjust the calculated coordinate.Margin properties
Color properties
Labels and text properties
dom
text in place of canvas
text. It makes for higher quality text that you can also select if desired (for copy/paste operations). It won't fit all situations and you can read more about the DOM text feature here. A good way to control borders/margins/padding etc is not to set them on the canvas
but to wrap the canvas
in a div
and set them on that like this:
<div style="margin-left: 50px; display: inline-block"> <canvas id="cvs" width="650" height="250"></canvas> </div>
visible
or hidden
and it controls whether the text is clipped to the edges of the canvas
. It defaults to be visible and means you can set small margins if you wish.dom
text responds to mouse-based events or not (it sets the pointer-events
css
property to none
).%{value_formatted}
macro.%{value_formatted}
macro.%{value_formatted}
macro.%{value_formatted}
macro.%{value_formatted}
macro.css
class to the labels which you can then use for styling purposes or to make retrieving the span
tags easier (the dom
elements). If you inspect the labels in your browser's javascript
console (you will first need to enable the textAccessiblePointerevents
property) you will be able to see the other css
classes that are assigned to the labels.v6.11
these labels are only shown if there's sufficient space in the segment for them. If there's not enough space for a particular label then that label isn't shown.strings
(with or without formatting macros) or it can also be a single string
, again, with or without formatting macros. Though when it's a single string
it does make plenty of sense to include some formatting macros. You can read more about what macros are available here.%{value_formatted}
macro.%{value_formatted}
macro.%{value_formatted}
macro.%{value_formatted}
macro.%{value_formatted}
macro.var undrawn = myPie.get('labelsIngraphUndrawn')
) after your Pie chart
has been drawn to find out which of your ingraph labels were not drawn because the label is too big for the segment. You could then use this to add regular labels that contain the information that you want to be displayed to the user. This way no information is lost when your ingraph labels are not shown. There's a demo of this in the download called pie-labelsingraphundrawn.html
true
.true
then the ingraph labels will always be shown - even if they don't fit into the segment.Donut charts
- if you want labels on your chart that are positioned inside the donut ring then set this to true
.auto
or center
. When it's set to auto
(the default) then the horizontal alignment will be left for labels on the left half of the chart and right for labels on the right side of the chart. When set to center
then you may also need to use the labelsInsideOffsetr
property to move the labels inwards.Pie chart
constructor are used as the labels. Using this property though you can specify exactly what the labels are. This can either be an array of strings (with or without formatting macros), which are used as the labels, or it can be a single string containing formatting macros (for example: labels: '%{property:myNames[%{index}]} (%{value_formatted}'
).%{value_formatted}
macro.%{value_formatted}
macro.%{value_formatted}
macro%{value_formatted}
macro.%{value_formatted}
macro.Title properties
textFont
setting is used (usually Arial
).4pt
bigger than the textSize
setting."-5"
- in which case it's converted to a number and added to the calculated coordinate - allowing you to adjust the calculated coordinate."-5"
- in which case it's converted to a number and added to the calculated coordinate - allowing you to adjust the calculated coordinate.marginTop
value.Shadow properties
Interactive features properties
html
.click
or mousemove
.slide
fade
or none
.true
to get this behaviour. Keep in mind that if you have a lot of bars/segments/points/etc then it's possible for the chart to become quite crowded. If you need to subsequently clear all of the tooltips there's an api
function available to do that for you and it's called: RGraph.tooltip.persistent.clear()
If you want to access any (or all) of the tooltip div
tags then you can do so using the RGraph.tooltip.persistent
object. This option works when you have the tooltipsEvent
property set to mousemove
%{value_formatted}
option.%{value_formatted}
option.%{value_formatted}
option.%{value_formatted}
option.%{value_formatted}
option.%{key}
option to use.square
or circle
css
values to the key color shape that appears in the tooltip key. Note the property name is "color" and not "colors" like previous properties. It should be an object of css
properties like this: tooltipsFormattedKeyColorsCss : { border: "1px solid #ddd"; }
ul
and ol
.tooltipsFormattedListItems: [ ['Bill','Jerry','Berty'], // First tooltip ['Gill','Carrie','Lucy'], // Second tooltip ['Pob','Nobby','Hilda'] // Third tooltip ]You can use
css
to style this list - for example:.RGraph_tooltip ul#rgraph_formatted_tooltips_list li { text-align: left; color: yellow; }
th
tags.css
values applied to the tooltips pointer (a css
border, for example) then specify an object containing those values to this property. For example: tooltipsPointerCss: { borderLeft: 'gray 2px solid', borderBottom: 'gray 2px solid' }
false
tooltips are positioned next to the mouse pointer.css
that gets applied to all of the tooltips, but don't want to use the RGraph.tooltips.style
object (which gets applied to all of the tooltips on the page for every chart) you can use this property to give some per-object css
for the tooltips. These are css
styles that get applied to all of the tooltips for the specific object only. It should look like this:tooltipsCss: { fontFamily: 'Verdana', fontSize: '20pt' }
css
class the chart uses.pie-tooltipshotspotignore.html
. You can use the transparent
color to allow the rear chart to be seen in such a case. It can be:
- A single
boolean
value (ietrue
orfalse
) to enable or disable all of the hotspots -true
means the hotspot will be ignored - A single number (the zero-indexed number corresponding to the hotspot to ignore)
- An array of numbers (the numbers are the indexes of hotspots to ignore)
- An array of
boolean
true
orfalse
values - the position of these values correspond to the index(es) of the segments to ignore (for example[false, false, true, false, false]
-true
means the corresponding hotspot will be ignored)
Key properties
The key properties are documented on the key documentation page.Miscellaneous properties
5
, and setting the colorsStroke
to the same color as your background color you will get a segment separation effect.pie
(the default), pie3d
, donut
or donut3d
. Setting this to donut
or donut3d
is how you get a Donut chart
.2d
, 3d
, outline
, invert
or a function and determines which style of segment highlighting is used in conjunction with tooltips. If it's a function the function is called and no highlighting is done - ie you should do it all yourself. As of version 5.23 you can also set this to invert
. If you do this on a dark background you may find that you need to change the highlight colors setting as well.highlightStyleTwodColor
.linewidth
of the highlight stroke.[0,5,0,0]
canvas
.Methods
obj.get(name)
An accessor that you can use to retrieve the values of properties.
obj.set(name, value)
An accessor that you can use to set the values of properties.
obj.getShape(event)
This method makes it easy to get hold of which segment has been clicked on or hovered over. It returns an object which has the following indexes available:
object |
The chart object |
x |
This is the center X coordinate for the segment. |
y |
This is the center Y coordinate for the segment. |
radius |
This is the radius of the segment. |
angleStart |
This is the start angle of the segment. It's measured in radians - not degrees. 1 radian = 57.29 degrees. |
angleEnd |
This is the end angle of the segment. It's measured in radians - not degrees. 1 radian = 57.29 degrees. |
dataset |
Since Pie charts can only have one dataset this is always zero.
|
index |
The zero-indexed index of the segment on the chart. |
sequentialIndex |
The sequentialIndex is the zero-indexed sequential index of the point on the
chart. Since, with Pie charts , there's only ever a single dataset this is always the
same as the index value.
|
tooltip |
If a tooltip is associated with this segment this will be it. id:
strings are expanded for you (where the tooltip text is retrieved from the html
tag with the matching ID).
|
<script> pie.canvas.onclick = function (e) { RGraph.redraw(); var canvas = e.target, obj = canvas.__object__, shape = obj.getShape(e); if (shape) { var x = shape.x, y = shape.y, radius = shape.radius, start = shape.angleStart, end = shape.angleEnd; obj.path( 'b m % % a % % % % % false c s black f red', x, y, x, y, radius, start, end ); } } </script>
obj.explode(index, size)
The explode
function allows you to programmatically
trigger the exploding (ie the highlighting of) a particular segment.
The explode
method is used like so:
<script>
pie = new RGraph.Pie({
id: 'cvs',
data: [8,9,4,6],
options: {
}
}).draw();
pie.explode(index, size);
</script>
The index argument is the zero-indexed segment to operate on (counting from the north axis). And the size is measured in pixels.
obj.getAngle(value)
This method can be used to get an appropriate angle for a value using
the "scale" of the Pie chart
. So if your Pie chart
is
showing values that go from 0-100 and your requested value is 50, this
method will return an angle for the bottom of
the Pie chart
(ie halfway around).
obj.on(event, function)
This method can be used to set an event listener on an object. It
operates similarly to the jquery
on
function.
The first argument is the event that you wish to attach to and the second
is the handler function. For example:
.on('draw', function (obj)
{
// Put your event code here
});
The function is useful if you use method chaining when creating your charts:
new RGraph.Pie({ id: 'cvs', data: [4,5,3,8,6,3], options: { } }).on('draw', function (obj) // Put your draw event code here }).on('click', function (e, shape) { // Put your click event code here }).draw()
obj.exec(function)
The exec function is documented here.
obj.responsive(configuration)
The responsive
function helps your charts
respond to different browser window sizes and screen
resolutions. For example, for smaller screens, you
might want to have angled labels or show shorter
versions of them completely.
Update: There is now the responsive configuration option available to you and this is now the preferred method of configuration.
The responsive function and configuration option are documented on their own page here.
The Horseshoe meter
The Horseshoe meter
is now (as of version 5.28) its own chart type and you can read about it on
the Horseshoe meter documentation page.
The Segmented donut
The Segmented donut is now (as of version 5.28) its own chart type and you can read about it on the Segmented donut documentation page.
The Activity meter
The CActivity meter is now (as of version 5.28) its own chart type and you can read about it on
the Activity meter
documentation page.
The RadialProgress meter
The Radial Progress
can be achieved by using the Activity meter
class and configuring it as
shown on the Activity meter documentation page.
The coordinates properties
There's two coordinates properties on the
Pie chart
and they're the
obj.angles
property and the
obj.coordsText
property.
-
obj.angles
This holds the information about the angles that make up the segments on the chart. The properties that each entry holds are:- start angle (measured in radians)
- end angle (measured in radians)
- center
x
coordinate - center
y
coordinate
-
obj.coordsText
This holds the coordinates of all of the text that has been added to the chart. Even if the text is blank (ie no text) then the coordinates will be added to this variable.
Events
RGraph supports custom events that allow you to easily add interactivity to your charts if required. The following events are available:
annotatebegin
This event fires at the start of annotating - like the standardmousedown
event.annotate
This event fires (repeatedly) during annotating - like the standardmousemove
event.annotateend
This event fires at the end of annotating - like the standardmouseup
event.annotateclear
This event fires at the end of theRGraph.clearAnnotations
function.beforeclear
This event fires at the start of theRGraph.clear
function.clear
This event fires at the end of theRGraph.clear
function.click
This is similar to the standardcanvas
click
event but this only fires when you click on a bar - not the wholecanvas
.crosshairs
This event fires when you have the crosshairs feature enabled and you move the mouse.beforecontextmenu
This event fires when you have the contextmenu enabled and it is about to appear.contextmenu
This event fires when you have the contextmenu enabled and it has been displayed.beforedraw
This event fires at the start of thedraw
method before anything has been done.firstdraw
This event fires at the end of thedraw
function - but only the first time that thedraw
function is called.draw
This event fires at the end of thedraw
function.beforeinteractivekey
When you're using the interactive key this event fires just before the key and chart are highlighted.afterinteractivekey
When you're using the interactive key this event fires just after the key and chart are highlighted.mousemove
This event is similar to the standardmousemove
event but only fires when you move the mouse over a bar on the chart.mouseover
This event is similar to the standardmouseover
event but only fires when you move the mouse over a bar on the chart.mouseout
This event is similar to the standardmouseout
event but only fires when you move the mouse away from a bar on the chart that you've previously hovered over.beforetooltip
This event fires at the start of the tooltip showing process.tooltip
This event fires after a tooltip has been shown.
new RGraph.Pie({ id: 'cvs', data: [4,8,6], options: { } }).on('draw', function (obj) { console.log('The draw event has fired'); }).draw();
Effects
These effects are available and can be used instead of thedraw
function. There are also generic effects
available which you can see here:
Generic effects and transitions
There's a stopAnimation()
function that you can
use to stop an animation immediately if you need to.
There's a line chart demo called
demos/line-effects-stop-animation.html
in
the download archive
that demonstrates the use of this function.
- The
grow
effect (effects-pie-grow.html
in the download archive) - The
explode
effect (effects-pie-explode.html
in the download archive) - The
implode
effect (effects-pie-implode.html
in the download archive) - The
roundrobin
effect (effects-pie-roundrobin.html
in the download archive) - The
roundRobinSequential
effect (effects-pie-roundrobinsequential.html
in the download archive) - The
wave
effect (effects-pie-wave.html
in the download archive)
<script> // // Optional callback function that's called when the effect is complete // function myCallback (obj) { // ... } new RGraph.Pie({ id: 'cvs', data: [8,6,6,5,3,4,2], options: { } }).grow({frames: 60}, myCallback) // .explode({frames: 60}, myCallback) // .implode({frames: 60}, myCallback) // .roundRobin({frames: 60}, myCallback) // .roundRobinSequential({frames: 90}, myCallback) // .wave({frames: 60}, myCallback) </script>