Card vs Sub Stack?

[Geoff Canyon]

At 3:33 PM +0000 1/7/02, Ben Rubinstein wrote:
>My $0.02, FWIW: I have an application such as this, and used seperate
>substacks for each type, mainly so that the different types could be edited
>in different windows.  It turned out that while some of my users appreciated
>this, some found it made their lives more confusing, and I ended up having
>to implement a 'pin windows' functionality which made all windows the same
>size and position (so that you could only see one at a time) and which
>arranged that when in this mode, dragging any (obviously the front most)
>would drag the others to the same position (so that they remained hidden
>behind it).  In effect this was reverting to the position of having separate
>cards of one stack.
>
>Depending on your userbase, more functionality may not imply more
>productivity.

Note that you can avoid this by using:

go stack "someOtherStack" in the window of this stack

That way only one stack window will ever be open, and you don't have to manage a bunch of windows.

regards,

Geoff