-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs: ui.combo_box #718
docs: ui.combo_box #718
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ready for re-review @margaretkennedy
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ready for re-review @bmingles @margaretkennedy
## API Reference | ||
|
||
```{eval-rst} | ||
.. dhautofunction:: deephaven.ui.combo_box |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since I see you have a new dhautofunction
here, please either
- Create the docs locally and verify they are created correctly (the easiest way to do this is via
tools/plugin_builder.py
, check out the readme and let me know if you have problems). - Wait until fix: Prevent pushing broken docs to main #719 is merged then merge main in to this branch so the docs will be checked automatically
Thanks
@@ -323,27 +327,37 @@ my_combo_box_event_example = ui_combo_box_event_example() | |||
|
|||
## Control | |||
|
|||
When a combo box has multiple controlled properties (e.g., `input_value`, `selected_key`), updates to one property do not automatically update the others. Each interaction triggers only its specific event handler. For instance, typing in the input field will only trigger the `on_input_change`, not the `on_selection_change`. | |||
Each interaction done in the ComboBox will only trigger its associated event handler. For instance, typing in the input field will only trigger the `on_input_change`, not the `on_change`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is true for typing, but it contradicts earlier docs when user selects a value, that does actually fire on_input_change
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking better. Looks like you may have accidentally committed a file? Also see the comment about an inaccuracy in ## Control
section
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Co-authored-by: margaretkennedy <[email protected]>
Closes #687