Timeline for Unwanted interaction between instances of a Manipulate function
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 13, 2017 at 12:55 | history | edited | CommunityBot |
replaced http://mathematica.stackexchange.com/ with https://mathematica.stackexchange.com/
|
|
| Mar 19, 2015 at 3:34 | history | tweeted | twitter.com/#!/StackMma/status/578399227669319680 | ||
| Mar 19, 2015 at 0:52 | vote | accept | murray | ||
| Mar 19, 2015 at 0:52 | vote | accept | murray | ||
| Mar 19, 2015 at 0:52 | |||||
| Mar 19, 2015 at 0:44 | comment | added | murray |
No, 2 or even half a dozen or more "test" functions would not suffice for building into the Manipulate: the idea is to create a function trajectory that can be used with *any" vector field function the user might wish.
|
|
| Mar 19, 2015 at 0:42 | history | edited | murray | CC BY-SA 3.0 |
added 636 characters in body
|
| Mar 19, 2015 at 0:32 | answer | added | Michael E2 | timeline score: 5 | |
| Mar 18, 2015 at 23:43 | comment | added | Nasser |
You are using Manipulate as a function. This is not really how Manipulate is meant to be used. Manipulate should be self contained. If you want to test 2 functions, make a Manipulate with pull-up menu and select one of the functions. In your example, first Manipulate detected f changed and updated. You do not need to even make a new manipulate call to see the interaction. Just defining f again in the global context will cause the Manipulate to change.
|
|
| Mar 18, 2015 at 22:53 | comment | added | Sjoerd C. de Vries | DynamicModule. | |
| Mar 18, 2015 at 22:22 | history | asked | murray | CC BY-SA 3.0 |