Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.soft-sys.math.mathematica > #13914

Manipulate and Initialization

From Fred Simons <f.h.simons@tue.nl>
Newsgroups comp.soft-sys.math.mathematica
Subject Manipulate and Initialization
Date 2013-03-23 07:24 +0000
Message-ID <kijlb0$is0$1@smc.vnet.net> (permalink)
Organization Time-Warner Telecom

Show all headers | View raw


I want to create a rather complicated Manipulate, in which I do not know 
the limits for the parameter beforehand; they depend on the result of an 
initialization. Here is a highly simplfied example:

Clear[nn];
Manipulate[n, {n,1,nn,1}, 
Initialization:>(nn=RandomInteger[{5,15}];Print[nn])]

This works fine. The slider can be used in the range from 1 to the 
printed value.

However, when nn already has a value, the behaviour is different. When 
we execute

nn=23;
Manipulate[n, {n,1,nn,1}, 
Initialization:>(nn=RandomInteger[{5,15}];Print[nn])]

a value between 5 and 15 for nn is printed, but that value is not used 
in the result; the slider now runs from 1 to 23.

So, whether nn has a value or not, just before the box structure is 
printed, the frontend asks the kernel to evaluate the initialization. 
But the returned value of nn is used in Manipulate only when nn did not 
have a value before. That embarasses me. Any explanation is highly 
apprectiated.

Fred Simons
Eindhoven University of Technology

Back to comp.soft-sys.math.mathematica | Previous | Next | Find similar | Unroll thread


Thread

Manipulate and Initialization Fred Simons <f.h.simons@tue.nl> - 2013-03-23 07:24 +0000

csiph-web