> I wanted to say that checking for cd 1 can work only if user deletes > properly all other cards first. For example, consider a stack with 3 > cards and user is on the last card. He deletes it, so the current > card becomes 1. Now your check will refuse to delete but clear cards > instead; however, there is still one more card left.
Agreed - better yet is to check: if the number of cards = 1 then > clear all fields is not a valid construct -- you need to empty one > field after another. And I'd also remind people that many of us use field labels in front of fields to describe them, or list fields that *shouldn't* be cleared... better yet would be to test the lockText or the listBehavior of each field before you clear it. Ken Ray Sons of Thunder Software Web site: http://www.sonsothunder.com/ Email: [EMAIL PROTECTED] _______________________________________________ use-revolution mailing list [email protected] http://lists.runrev.com/mailman/listinfo/use-revolution
