Timeline for Manipulate lists as function arguments
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 8, 2020 at 12:39 | comment | added | Mr.Wizard |
@Stephen (1) According to the specification of Manipulate: "The form {u, umin, umax, func} can also be used; what is evaluated is then func[Dynamic[u], {umin, umax}]." Since it is already passed in a Dynamic head thought perhaps nesting a second one was a source of trouble. (2) I feel like this should just work and wondered if it was a version-specific bug. I don't know how to get it working, and the fact that you're trying to do this for a Demonstration adds restrictions that make alternatives difficult.
|
|
| Jan 8, 2020 at 1:32 | comment | added | Stephen Eubank | Huh, this exhibits the same behavior, too: h[Dynamic[point_], opt___] := Dynamic[HorizontalGauge[Dynamic[point]]] I just hadn't tried clicking outside the markers. | |
| Jan 8, 2020 at 1:11 | comment | added | Stephen Eubank | In version 12.0.0.0 on MacOS 10.13.6 I get what sounds like the same behavior. When I click in the gauge, the nearest marker moves to the position I clicked and the value of pt is updated. Dragging does nothing. Thanks, I can make this work in a pinch. Can you explain why the argument of h is not inside a Dynamic? Do you think it might be worth fiddling with mouse events to try getting click-and-drag to work? | |
| Jan 7, 2020 at 22:32 | history | answered | Mr.Wizard | CC BY-SA 4.0 |