Opened 7 years ago
Last modified 5 weeks ago
#14020 needs_review defect
interact with layout is broken
Reported by: | novoselt | Owned by: | jason, mpatel, was |
---|---|---|---|
Priority: | major | Milestone: | sage-duplicate/invalid/wontfix |
Component: | notebook | Keywords: | interact sd48 |
Cc: | jason, kcrisman | Merged in: | |
Authors: | Reviewers: | ||
Report Upstream: | N/A | Work issues: | |
Branch: | Commit: | ||
Dependencies: | Stopgaps: |
Description
Consider this example:
@interact(layout={ "top": [ ["u_lines"], ["v_lines"], ] }) def _( u_lines=slider([1..50], default=10, label=r"$u$-lines:", display_value=False), v_lines=slider([1..50], default=10, label=r"$v$-lines:", display_value=False), ): print u_lines, v_lines
With 5.7.beta1 (and I believe the problem existed for a while):
- The vertical spacing between elements is HUGE - if I remove layout (which is supposed to reproduce default placement here anyway), it is much more reasonable. This makes it next to impossible to create interacts to show in class that will have all controls and graphs on one screen in a reasonable size.
- Math is not processed in labels. Again, everything is OK without layout.
- Values of sliders are not actually updated - this is due to
display_value=False
with or without layout.
In Cell Server there are no issues with layout, but display_value=False
does not work - the value is still shown.
Change History (9)
comment:1 Changed 7 years ago by
- Cc kcrisman added
comment:2 Changed 7 years ago by
comment:3 Changed 7 years ago by
- Keywords sd48 added
comment:4 Changed 7 years ago by
- Milestone changed from sage-5.11 to sage-5.12
comment:5 Changed 6 years ago by
- Milestone changed from sage-6.1 to sage-6.2
comment:6 Changed 6 years ago by
- Milestone changed from sage-6.2 to sage-6.3
comment:7 Changed 6 years ago by
- Milestone changed from sage-6.3 to sage-6.4
comment:8 Changed 5 weeks ago by
- Milestone changed from sage-6.4 to sage-duplicate/invalid/wontfix
- Status changed from new to needs_review
sagenb is now deprecated
comment:9 Changed 5 weeks ago by
Does this work on Jupyter? We could repurpose the ticket. And the syntax is "supposed to work" on platforms ...
Note: See
TracTickets for help on using
tickets.
https://github.com/sagemath/sagenb/pull/168 solves the first two bullets