aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authormrfaptastic <12006953+mrfaptastic@users.noreply.github.com>2020-08-03 14:11:50 +0100
committerGitHub <noreply@github.com>2020-08-03 14:11:50 +0100
commit5caea964241ed7c4cfe93e94f2eacf04a2639a62 (patch)
tree93421693c35543e05e817bebc4fc58622fd01b9b
parentd1dfa833037420aad9c48732ee229554fa88f261 (diff)
Update README.md
-rw-r--r--README.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/README.md b/README.md
index 0981624..50462ea 100644
--- a/README.md
+++ b/README.md
@@ -66,7 +66,7 @@ A [typical RGB panel available for purchase](https://www.aliexpress.com/item/256
Yes you can. If you want to use with a 64x64 pixel panel (typically a HUB75*E* panel) you MUST configure a valid *E_PIN* to your ESP32 and connect it to the E pin of the HUB75 panel! Hence the 'E' in 'HUB75E'
-This library has only been tested with a 64 pixel (wide) and 32 (high) RGB panel. Theoretically, if you want to chain two of these horizontally to make a 128x32 panel you can do so with the cable and then set the MATRIX_WIDTH to '128'. Refer to the [Chained Panels](examples/ChainedPanels/) example.
+This library has only been tested with a 64 pixel (wide) and 32 (high) RGB panel. Theoretically, if you want to chain /n/ of these horizontally to make a (n*64)x32 panel you can do so with the cable and then set the MATRIX_WIDTH to '64*/n/'. Refer to the [Chained Panels](examples/ChainedPanels/) example.
## Ghosting