Skip to content

Commit f53a4ec

Browse files
author
gemi254
committed
Updated v1.1.6
1 parent 76a628d commit f53a4ec

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -68,7 +68,7 @@ Define and initialize you class
6868
- `ctrl.bind("html_id", start_value );` if you need to bind and init for sending on connection
6969
- `ctrl.bind("html_id", start_value, changeFunction);` if you need also to handle changes
7070

71-
+ in your setup specify if you want ot auto send key initial values during web socket connection.
71+
+ in your setup specify if you want to auto send key initial values during web socket connection.
7272
- `ctrl.setAutoSendOnCon("html_id",true /* send: enable/disable */);`
7373
- `ctrl.put("html_id", value); // Set a default value to be send`
7474

@@ -108,7 +108,7 @@ Controlling your elements inside you loop function
108108
+ Inside your main loop() call ControlAssist loop() to handle web sockets server clients
109109
- `ctrl.loop();`
110110
111-
##### Note that when a html control is "binded" (linked to some backend variable), the library checks whether the new value in ctrl.put differs from the previous send or initial value. If there’s no change, ControlAssist by default does not resend the same value to conserve bandwidth. You can use ``forceSend`` in ctrl.put to send even no change. This optimization is particularly important in applications where frequent updates could lead to performance bottlenecks or excessive network usage (e.g., sliders, real-time monitoring systems, or IoT dashboards).
111+
##### Note that when a html control is "binded" (linked to some backend variable), the library checks whether the new value in ctrl.put differs from the previous send or initial value. If there’s no change, ControlAssist by default does not resend the same value to conserve bandwidth. You can use ``forceSend`` in ctrl.put to send even if there is no change. This optimization is particularly important in applications where frequent updates could lead to performance bottlenecks or excessive network usage (e.g., sliders, real-time monitoring systems, or IoT dashboards).
112112
113113
114114
## JavaScript handlers inside your webpage

0 commit comments

Comments
 (0)