summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorFuzzy <ulima.ums@googlemail.com>2015-02-22 00:55:04 +0100
committerFuzzy <ulima.ums@googlemail.com>2015-02-22 00:55:04 +0100
commit812b27b3fc8589988b588a19e901b0c5704d873d (patch)
tree240ecad3bc8d257147c145ff981ca52cd463612e
parent93c7b3af51c68f3d2cb37ff41c0eb941e1b81df6 (diff)
parentc3eb2591d2d5e3523c8e04ce263fcf55b31c861c (diff)
downloadsvg.js-812b27b3fc8589988b588a19e901b0c5704d873d.tar.gz
svg.js-812b27b3fc8589988b588a19e901b0c5704d873d.zip
Merge pull request #273 from dotob/patch-1
add missing add in function params
-rwxr-xr-xREADME.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/README.md b/README.md
index 01c36e9..9949340 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')
})
```