From c6a63dec25abb1ff9cdd4eebc5d6df9134be99d7 Mon Sep 17 00:00:00 2001 From: Eric Klavins Date: Fri, 6 Mar 2020 11:15:50 -0800 Subject: [PATCH] new tags --- README.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/README.md b/README.md index 542aceb..6749213 100644 --- a/README.md +++ b/README.md @@ -244,6 +244,7 @@ The port for the server. Use `8765` for now. > ``` > The name field is used to catch button click events (see below). The label field defines the string displayed on the button. > The style field is an `css` code you want to add to the stying of the button. +> (New in 1.0) > `agents`
> A list of agents to put in the simulation. For example, @@ -288,6 +289,7 @@ The brower client relays mouse click, button press, and keyboard events to the e > Name: `button_click` > Value: An object with the a `name` field that matches the name field used in `config.json`. +> (New in 1.0) > Name: `keydown` > Value: An object with a `key` field, which is the character pressed, as well as the following boolean fields @@ -297,9 +299,11 @@ The brower client relays mouse click, button press, and keyboard events to the e > altKey > metaKey > ``` +> (New in 1.0) > Name: `keyup` > Value: Same as for `keydown`. +> (New in 1.0) To respond to events in your code, you should put elma watchers into the `init()` method of some process. For example, to respond to an agent click, you might do ```c++