Jim.Russell@f421.n109.z1.fidonet.org (Jim Russell) (02/02/91)
I've noticed an unexpected behavior in HC 2.0v2 which can be simply
reproduced: Create a new stack with 3 cards of the same background;
create the background script:
on deleteCard
go prior card
end deleteCard
And note that cards cannot be deleted. I suppose it might be a feature
if you want to work hard to keep from deleting cards, but it plays hell
when you want to avoid HC's normal practice of opening the next card
after a delete. (At least 2.0 now at least sends the open card message
in that instance!) I have a need to control the card that appears after
a delete, and discovered this behavior only when a go card id foo failed
because foo happened to be the card prior to the target of the delete
card menu command.
Anybody else seen it? Anybody got a fix or workaround?
--
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/401Jim.Russell@f421.n109.z1.fidonet.org (Jim Russell) (02/07/91)
The code seems a tad convoluted, but your suggestion is a good one --
delaying the move to the (new) till the openCard message ought to work
fine. Thanks.
--
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