Skip to content

Commit

Permalink
Apply suggestions from code review
Browse files Browse the repository at this point in the history
Apply suggestions
  • Loading branch information
jrobinAV authored Oct 19, 2023
1 parent 2033f4a commit 28dae71
Show file tree
Hide file tree
Showing 2 changed files with 3 additions and 3 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -67,15 +67,15 @@ ensuring that changes made by one client don't affect others.

## Callbacks

You can include [Callbacks](../../../../manuals/gui/callbacks.md) in each visual element,
Most visual element include [callbacks](../../../../manuals/gui/callbacks.md),
enabling you to modify variables according to user actions. For further details, explore local
callbacks and global callbacks.

- *state*: The state object containing all the variables.
- The name of the modified variable. (optional)
- Its new value. (optional)

Here's an example of `on_change()` function to update *state.dataset_week* based on the selected
Here's an example of of setting the `on_change` callback function to update *state.dataset_week* based on the selected
week from the slider:

```markdown
Expand Down
2 changes: 1 addition & 1 deletion docs/knowledge_base/tutorials/cycles_scopes/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -245,7 +245,7 @@ Scenario 2: Primary? False True
### Scenario management visual elements

You can use Scenario management visual elements to control Cycles. Cycles can be seen in either the
*scenario_selector* or *data_node_selector*. Additionally, it's possible to designate a scenario
`scenario_selector` or `data_node_selector`. Additionally, it's possible to designate a scenario
as primary directly through the `scenario` visual element.

```python
Expand Down

0 comments on commit 28dae71

Please sign in to comment.