I saw your construction of two stacks displayed in a "frame", so it appeared
that two cards were simultaneously present in a single "stack".
I see what you are after; the goal being be able to navigate in each card
Why only two?
Anyway, I have never needed such a feature, but certainly see that others
might. I often open substacks (or other stacks) on screen, generally for a
particular purpose ancillary to the working stack, and close them when done.
They are in that case just a high-powered dialog box, used basically in the
I remember when HC allowed up to 16 open stacks, as opposed to just one. A
A multi-visible-card stack would be useful for multimedia displays, and
likely for other purposes. It sounds like a major effort, though, addressing
the foundations of the program itself.
> I know the idea of being able to display different cards from one
> stack in different windows is something that has exercised many
> people for a long time.
> I had a fantasy that ran like this:
> show card 6 of stack "Stack1" in stack "subStack1"
> How daft is that?
No more daft than Gain Momentum, a powerful xTalk I worked with back in
the day that had an object type called Viewers that did exactly what you
Fourth World Systems
Software Design and Development for the Desktop, Mobile, and the Web
I do the same thing. There is no downside to using substacks or other stacks, but you can open a stack in a current window.
> On Mar 31, 2018, at 08:25 , dunbarx via use-livecode <[hidden email]> wrote:
> Anyway, I have never needed such a feature, but certainly see that others
> might. I often open substacks (or other stacks) on screen, generally for a
> particular purpose ancillary to the working stack, and close them when done.
> They are in that case just a high-powered dialog box, used basically in the
> same way.