aboutsummaryrefslogtreecommitdiffstats
path: root/README.md
diff options
context:
space:
mode:
authorsebastian krämer <sk@dotob.de>2014-10-13 10:27:06 +0200
committersebastian krämer <sk@dotob.de>2014-10-13 10:27:06 +0200
commitc3eb2591d2d5e3523c8e04ce263fcf55b31c861c (patch)
tree9c9f1cf4d783d3090639f2674f126e44afddaaf8 /README.md
parent7984a87786effaed2ed6e517c899cc68204e4e6b (diff)
downloadsvg.js-c3eb2591d2d5e3523c8e04ce263fcf55b31c861c.tar.gz
svg.js-c3eb2591d2d5e3523c8e04ce263fcf55b31c861c.zip
add missing add in function params
Diffstat (limited to 'README.md')
-rwxr-xr-xREADME.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/README.md b/README.md
index 8066600..99832ab 100755
--- a/README.md
+++ b/README.md
@@ -2395,7 +2395,7 @@ path.marker('end', 20, 20, function(add) {
The `marker()` method can be used in three ways. Firstly, a marker can be created on any container element (e.g. svg, nested, group, ...). This is useful if you plan to reuse the marker many times so it will create a marker in the defs but not show it yet:
```javascript
-var marker = draw.marker(10, 10, function() {
+var marker = draw.marker(10, 10, function(add) {
add.rect(10, 10)
})
```
@@ -2403,7 +2403,7 @@ var marker = draw.marker(10, 10, function() {
Secondly a marker can be created and applied directly on its target element:
```javascript
-path.marker('start', 10, 10, function() {
+path.marker('start', 10, 10, function(add) {
add.circle(10).fill('#f06')
})
```