Timeline for What is the difference between Dynamic[x] and Dynamic[ h[x] ] for DynamicModule variables?
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 5, 2016 at 10:21 | comment | added | Jacob Akkerboom |
@Kuba I suppose this also means that the front end "backtracks" if it finds an expression it cannot call ToBoxes on itself, and even though it has evaluated the expression inside ToBoxes, it sends the entire unevaluated version of the expression with head ToBoxes over to the kernel.
|
|
| Oct 5, 2016 at 10:19 | comment | added | Jacob Akkerboom |
@Kuba ok, so it seems the Front End can handle ToBoxes[1], but not ToBoxes[{1}]
|
|
| Oct 5, 2016 at 10:19 | history | edited | Jacob Akkerboom | CC BY-SA 3.0 |
Nicer example, better text
|
| Oct 5, 2016 at 9:00 | comment | added | Jacob Akkerboom | @Kuba you make a good point, I am once again confused :P | |
| Oct 5, 2016 at 8:49 | comment | added | Jacob Akkerboom |
@Kuba I have to think about that, but please see my awesome last example, which fixes the mismatch between the x in the kernel and the x in the Front End
|
|
| Oct 5, 2016 at 8:47 | history | edited | Jacob Akkerboom | CC BY-SA 3.0 |
Funky example
|
| Oct 5, 2016 at 8:35 | comment | added | Kuba |
{x} needs Kernel for typesetting (List), not evaluation (x). It is the same as here: Dynamic[CurrentValue[{"MousePosition"}]], this is sent to the Kernel but it doesn't have to, try: Dynamic[CurrentValue[{"MousePosition"}][[1]]]. CellEventActions are arguable but Button's evaluation is a clear case. There is a flaw in a synchronization scheme. Synchronization between kernel evaluation and updating the state of Dynamic Objects.
|
|
| Oct 5, 2016 at 8:30 | history | edited | Jacob Akkerboom | CC BY-SA 3.0 |
[Edit removed during grace period]
|
| Oct 5, 2016 at 8:21 | history | edited | Jacob Akkerboom | CC BY-SA 3.0 |
added 1 character in body
|
| Oct 5, 2016 at 8:05 | history | answered | Jacob Akkerboom | CC BY-SA 3.0 |