If the cards are moving back and forth between the decks fine then the numPieces property should be adjusting also but it sounds like it is not. Could be a trait stack order issue, but without seeing it I cant be sure. Do the cards have any types of ownership associated with them? May be another reason
Tim _____ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of David Neumann Sent: Monday, July 30, 2007 10:46 AM To: [email protected] Subject: [vassalengine] Strange Deck issue Hi all, This is strange, and I'm hoping someone might be able to give me some advice without looking directly at the module...so, lets see. I have 2 decks on a board. Both are discard decks, 1 intended for cards to be played face-up the other face-down. No problem so far. I can drag cards to each deck now, and transfer cards between decks without any issue. Now, I want to apply a trigger to the cards which basically keeps track if the card was ever in the 'face-up' discard deck. I have a dynamic property set to false, which I trigger to become 'true' when the card is placed in the face-up deck. This works great, but what I've noticed, is that the cards seem to become 'stuck' when I add this trigger. I can move cards to the decks, but then only the top card is movable and the others are not. I can select them (see the black selection rectangle) when I click the deck, but cannot move them. Again, I can move the top card in the deck. I used a text-label to watch the <name>_numPieces variable, and the cards that are 'stuck' are not adding to the number of cards in the deck. If I remove this trigger, the cards are movable between decks again. I know this is strange, but I'm hoping some of the VASSAL gods here might know what is happening without me sending them the mod. Thanks for your help, Dave Neumann [Non-text portions of this message have been removed]
