Thanks for the response.
> Hi Tim,
>
> The "Key Command to apply to all units ending movements on this map" is
> only designed to apply to drag and drop movement.
I suppose it should be called "apply to some units ending movements on
this map" then? :)
>
>
>>*********** REPLY SEPARATOR ***********
>>
>>On 21/09/2006 at 11:45 PM Tim Byrne wrote:
>>I'm not sure of the short way to refer to this feature, but I'm talking
>>about the option for maps called "Key Command to apply to all units
>> ending
>>movements on this map". This feature does not work consistently for all
>>pieces. I have observed that while in general this feature works, it the
>>Key Command doesn't get triggered in particular situations:
>>a. Send To Location: When moving a piece using this trait, the map based
>>key command is not triggered.
>>b. Move Fixed Distance: When moving a piece using this trait, the map
>>based key command is not triggered.
>
> The two are KeyCommand based movement that can be picked up with a Trigger
> Action.
I realize that (and I have done that as a work around) but then I have to
do a bunch of extra definition when it seems to me that anything that
moves on the map window should get triggered.
>
>>c. When moving a piece into a Deck, the map based key command is not
>>triggered. However, when you move a piece with the Does Not Stack trait
>>into a Deck, it IS triggered.
>
> Do you mean physcially drag and drop a piece onto the deck, or using
> 'Return to Deck', 'Send to Location' or 'Moved Fixed Distance'. The latter
> will not work as outlined above. If the former, the action may be
> suppressed when movement ends in a Deck.
I mean physcially draging and dropping. Download my test modules and try
for yourself.
>
> When the 'Does Not Stack' piece is moved to the deck, does it actually go
> into the Deck, or is it sitting under the deck and not stacked into it?
It goes in the deck. I can tell, because I can change the deck to "allow
specific cards to be drawn" and they all show up in the list.
>
>
>>d. When moving an existing piece onto a stack of other pieces, the map
>>based key command is not triggered.
>
> It certainly should be triggered for drag and drop movement in this
> situation. Are you sure about this one?
Yes, download my test module and see for yourself. I drag a bunch of my
stacking pieces into a stack, and then drag an already created stackable
piece onto that stack, and its not triggered.
In the end what I'm really after is a way to (in general) automate some
things all the time. The best shot at that from my knowledge, is to
trigger GKC whenever things move. I'm just finding that there are times
that things move and they don't trigger the command :(
-Tim
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/vassalengine/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/vassalengine/join
(Yahoo! ID required)
<*> To change settings via email:
mailto:[EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
