Jim.Russell@f421.n109.z1.fidonet.org (Jim Russell) (11/13/90)
> If anyone has write capability to a stack, HyperCard 2.0 does > not allow anyone else to open it. If you lock the stack from the > Finder, then more than one person can open it at the same time -- and > no one will have write capability. Bummer - have we lost capability from HC 1.2.5? Is there some way the first users can specify they do not need write access? This is going to make an upgrade from the old behavior much harder, if I understand the description you gave. -- Jim Russell, Jim.Russell@f421.n109.z1.fidonet.org via The Black Cat's Shack's FidoNet<->Usenet Gateway blkcat.fidonet.org and Fidonet 1:109/401
jkc@Apple.COM (John Kevin Calhoun) (11/14/90)
In article <2405.273FD24A@blkcat.fidonet.org> Jim.Russell@f421.n109.z1.fidonet.org (Jim Russell) writes: >> If anyone has write capability to a stack, HyperCard 2.0 does >> not allow anyone else to open it. If you lock the stack from the >> Finder, then more than one person can open it at the same time -- and >> no one will have write capability. >Bummer - have we lost capability from HC 1.2.5? Is there some way the >first users can specify they do not need write access? This is going to >make an upgrade from the old behavior much harder, if I understand the >description you gave. No, there's no lost capability. HyperCard 1.2.5 works the same way. Kevin Calhoun HyperCard Team Apple Computer, Inc.
Jim.Russell@f421.n109.z1.fidonet.org (Jim Russell) (11/18/90)
It took me a bit to shake out the confusion, because we have been enjoying the multi user HyperCard behavior that you and the 1.2.5 upgrade notices assure us was never there and isn't there in HC 2.0 - namely the ability of the first user of a stack to perform updates, but for subsequent users to see the stack as locked. It is a very useful capability, but we were enjoying it thanks to TOPS - version 2.1 lets the first user see a file as read/write, but locks the file for subsequent users. I can see places where this might create problems, and it is beginning to look like TOPS 3.0 might be taking a different approach. -- Jim Russell, Jim.Russell@f421.n109.z1.fidonet.org via The Black Cat's Shack's FidoNet<->Usenet Gateway blkcat.fidonet.org and Fidonet 1:109/401