LiveCode Forums.

Trust me to hit a point where HyperCard differs from LiveCode and
Danny Goodman's books is silent.

I have a stack with 2 fields: "fABC" and "f123" on a card called "KARD".

The card contains this script:
- -
and I get this response when I press a key:
- -
which has thrown me "right off."

And bkgnd seems an odd abbreviation for background . . .

Probably time I stumped off to feed my alcoholic habit.

Word of the week: Curmudgeonly.

NOT exactly intuitive, but got "there" in the end:
-

Richmond.

You did everything but say what is was the threw the error. Perhaps it lies in the fact that in HC there are two kinds of fields, "card" and "Background"?

Craig

What threw the error was that, initially, my fields were just on the card, and the cardScript, for some reason, did not
want to put data into them and demanded backGround fields.

As the last time I did anything vaguely serious with HyperCard was in 1998 I had forgotten about HOW to make backGround
fields, so spent some time fooling around working out how to do that.
-

Even if nothing else my "side trip" with HyperCard has shown me how much easier the LC GUI is and how
far it has advanced.

It wasn't really demanding a background field, but it was expecting one. If not specified, HC fields are assumed to be background fields. Buttons are assumed to be card buttons. Since the handler didn't specify the error reported no bg field.

You could fix that by specifying the layer:
Put KD after cd field...

Richmond.

Background fields and card fields depend on whether the background is selected when a new field created. It is sort of a separate environment, selected via "cmd-B". Once in background mode, any new field will be a background field. In "normal" mode, any new field will be a card field.

It took me a while to get used to the fact that in LC, there was no background object, and only one kind of field. And that groups were required to emulate the background "behavior" in LC.

But now the old HC way seems outdated, I love that there is only one kind of field, and I have gotten used to groups with their backGroundBehavior set.

Craig

I also like that you can have more than one bg group on a card.

Jacque.

Yes. The "compartmentalization" of the background paradigm with groups allowed that. I used to hate the change. But like most changes, it is not a big deal any longer.

Craig