however cool the machinations of massaging a global under script control, why
do this at all? This is what custom properties are for; they also are
"global", and even better, they survive sessions.
Craig
--
Sent from:
http://runtime-revolution.278305.n4.nabble.com/Revolution-User-f278306.html
On 8/10/19 12:00 PM, David Epstein via use-livecode wrote:
I want to write a function that will read and write to any named global. What
I have below seems to work, but I’m not sure quite why. Usually, “put gName
into oldVal” for a global named gName would put the value, not the name, of
tha
I want to write a function that will read and write to any named global. What
I have below seems to work, but I’m not sure quite why. Usually, “put gName
into oldVal” for a global named gName would put the value, not the name, of
that global into oldVal. But here it does not.
function global
