You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While in majority of cases DynamicModule[{x},.. will be typeset to
DynamicModuleBox[{ $CellContext`x$$ }, ...
the majority of users will not know that. So if the UI creator used x the name should remain "x"
But since
I know one compose DynamicModuleBox manually but I have never heard of it being done.
One could also do DynamicModule[ { MyPackage`x, x },
Or authors of w-n-e may want to be strict.
We need to meet middle way.
So I propose the name to be user friendly and trying to match $CellContext`x$$ and friends while fullName being strict full name for an explicit match only and for a full control for edge cases.
The text was updated successfully, but these errors were encountered:
Yes, this is a good idea. We will change the behavior as proposed: By default, we will not require an "exact" name match anymore, i.e. implicitly normalize the given variable name (x -> $CellContext`x$$), like it happens behind the scenes for DynamicModule. We will introduce a parameter useExactName (default false) that you can set to true to get the current behavior, for full low-level control (although I don't think that should really be necessary).
A feature request
While in majority of cases
DynamicModule[{x},..
will be typeset tothe majority of users will not know that. So if the UI creator used
x
thename
should remain"x"
But since
We need to meet middle way.
So I propose the$CellContext`x$ $ and friends while
name
to be user friendly and trying to matchfullName
being strict full name for an explicit match only and for a full control for edge cases.The text was updated successfully, but these errors were encountered: