Scrolling List loses selection when switching card

[FourthWorld]

You could also use a non-lost field as a list by scripting the hilite using a graphic object set to the current hilite color.

Personally, I prefer to let the engine handle common behavior they've built in support for.

[richmond62]

a non-lost field

You, what?

[Klaus]

A non-LIST field!

As one could make out from the context of this thread.

[richmond62]

A non-LIST field!

As one could make out from the context of this thread.

Ah, but I was "list".

You could also use a non-lost field as a list

Err . . . and I could also use a large lump of blue-cheese as a table.

I wonder what the point of that remark was?

[FourthWorld]

To encourage newcomers to let the engine handle common tasks where it can, and save scripting for the things not already built into the engine.

[bogs]

To encourage newcomers to let the engine handle common tasks where it can

...and to give you a nibble of table at the seat near the cheese. I can offer you a very nice Cabernet to go with that table your sitting at...

[richmond62]

let the engine handle common tasks where it can

That would be marvellous if all the instances where the engine can handle common tasks
were adequately documented in a way that "newcomers" could understand.

[FourthWorld]

SharedText is documented to share text within a field when the field resides in a group that's been placed on multiple cards.

The ability to share a group across multiple cards is documented as being governed by the sharedBehavior property.