LiveCode Forums

I'm not quite a fan just yet. I simply declared and initialized a global at the main stack:

global deckImg
put 1062 into deckImg


There is no value in the global in my mouse handler....

Regards.

Al?

If I copy your two-liner verbatim into a button script and run it, nothing bad happens. And then if I go to the message box and invoke this:
I get "1062".

So the global was declared and remembered. Yay. Not sure what you are seeing.
All you really need, I will wager, is a bit more practice. And patience. Perhaps you might post your handler. I hope you will be a fan one day soon.

Craig newma

hmmmm... Gots to know where to look Simon

Global declared in my main stack script:

global deckImg
put 1062 into deckImg


code in my Mouse hander:
on mouseUp
answer deckImg
if the icon of me <> the backImg of me then
set the icon of me to the backImg of me
else
set the icon of me to the iconImg of me
end if
end mouseUp


Result:
deckImg

Tried this code in the handler:
answer the deckImg of this stack

Result:

blank screen

ahhh, you have to declare the variable in the mouseUp code as well.

Simon

Say what? A global, is a global, is a global!

Where you able to find the 1062 in the Variable tab?

And yeah, like the code you wrote first it must be declared in both places.

Simon

ok..I changed my handler to this:

on mouseUp
global deckImg
if the icon of me <> deckImg then
set the icon of me to deckImg
else
set the icon of me to the iconImg of me
end if
end mouseUp

my main stack still has:

global deckImg
put 1062 into deckImg

Result:

My button has no image everyother time I toggle it....

Easier way But that may not work with your setup. It would be like a Start/Stop button.

Simon

Globals must be declared in every script they are accessed, and ABOVE any handler within that script that uses them. This has cropped up before, from users of other languages, where any declaration at all becomes ubiquitous within the application.

But not in LC.

I am going to submit a feature request on this subject. It has been true for 28 years. I all of a sudden cannot see any advantage to having to do that.

Anyway, LC contains another, far more powerful feature, custom properties. These need only be set once, and thereafter are available anywhere, and survive sessions. They may contain a far greater range of data than globals, and may be accessed within a line, just as globals are. This discussion has also been well traveled...

Hi Al,

my main stack still has:

global deckImg
put 1062 into deckImg

is this inside of a "pre-/openstack" handler?


Best

Klaus

Hi Klaus, no I defined the global in the Main Stack, no handlers; a true global should not have to be defined in a handler..

Craig, yes it doesn't make sense (to programmers anyway) to have to declare a global again, once declared at the top of the stack. Yes I had defined the image value in a custom property so that the button's original image could be replaced upon toggle...

I finally got this to work yesterday, but for some reason, I had to close and reopen the Stack and it started working.

Thanks guys for your replies.

Regards.

Hi Al,

bigal60 wrote:Hi Klaus, no I defined the global in the Main Stack, no handlers; a true global should not have to be defined in a handler..

AHA!

OK, that's why it does not work, this needs to be "triggered" somehow inside of a handler. Put this into the stack script: Best

Klaus

Klaus,

This worked, however, I had to close and reopen the Stack before the change would take effect. What's up with that?

owever, I had to close and reopen the Stack before the change would take effect

Are you sure you compiled the script? Or saved the stack, which does the same thing.

Craig