# Tag Info

4

There are a number of issues here: There is no need to wrap Dynamic around the inner variables of the final input field expression. Indeed, it is harmful as Dynamic is purely a user interface element and acts as a holding wrapper in any other context (like an arithmetic expression). The use of Function in the output expression will cause the variables x ...

3

This is how I'd do that: DynamicModule[{coords, edges, lines, centers, locators}, Dynamic[ Graphics[{ GraphicsComplex[coords, { {Line[edges]}, {Darker@Red, PointSize[0.02], Map[Point, Range[5]]}}] , MapIndexed[locators, lines] } , ImageSize -> 400, Frame -> True, PlotRange -> 2] , None] , Initialization :> ...

3

This measures frame rate using simple Manipulate that does very little computation other than calculating FPS and then display an image. It finds fps as number of refreshes made so far divided by number of seconds elapsed. I did not use a moving average here, just kept a record of the number of times Manipulate is called and the time since start. This ...

1

Your code creates the following Locators, as stored in the Front End in its box form: {LocatorBox[ Dynamic[$CellContextbetweenPnt[{1.08, 0.94}, {1.08, 0.036}, 0.5]]], LocatorBox[ Dynamic[$CellContextbetweenPnt[{1.08, 0.94}, {0., 0.97}, 0.5]]], LocatorBox[ Dynamic[\$CellContext`betweenPnt[{1.08, 0.036}, {1.94, 0.49}, 0.5]]], LocatorBox[ ...

1

The behavior you describe is the normal behavior for expressions displayed dynamically. For example, if you create a 3D graphics object, evaluate it, rotate the object in the output image with the mouse, and delete the output, when you re-evaluate the 3D graphic, the new output image appears in the rotated position of the deleted image. To clarify the ...

Only top voted, non community-wiki answers of a minimum length are eligible