Hi to all.
Is it possible to introduce a waiting time between the execution of one trigger action and the following one, or, alternatively, to introduce a stop before executing the next trigger action? All trigger actions are performed in rapid succession and it is only possible to see the final total effect and not the intermediate ones.
Tank you for your support on this matter.
Panther_2010
I did try to do this, but had no success. I was only able to hang the UI for a time with no refresh.
What is your aim? To implement some sort of animation?
You could do an âemptyâ trigger action with an associated report trait that contains an Alert. E.g., your primary trigger is A, which should do B and C, but you want a pause between B and C.
A -> B -> C
So letâs introduce another trigger action D between B and C, and a report trait R that reacts to D
A -> B -> D (triggers R) -> C
and R contains an Alert line in the report attribute. This should make the trigger chain stop after D and wait for the user to dismiss the Alert pop-up. The D trigger action has no actionKeys.
Anyways, my 2 ¢ - havenât tried it.
Yours,
Christian
That works, and Alert() is the only way to do it.
In one of my modules, flipping over exploration tokens has one of a few effects that each require some bookkeeping, and the token is immediately discarded. Instead of relegating everything to a report, I had an alert pause so the face up token could be seen, and the effects announced. When the player clicks OK, everything is resolved.
Whether this is better than just cutting out the additional click and reporting what happened is debatable, but it works.
Couple of random blind and probably off-the-mark ideasâŚ
What if Alert() were cloned and the message parts replaced by the delay functionality ?
Is this any help or are you beyond that ?
The case I was investigating was trying to make it happen between actions in a single trigger. Having delays between different triggers is a different issue.
@Benkyo are you saying that running a series of different triggers, an Alert() in a later trigger reveals the changes from the Triggers up to that point?
@panther_2010, which where you looking for? Delay (with refresh) between triggers or between Key Commands in a single trigger?
What if Alert() were cloned and the message parts replaced by the delay functionality ?
If Alert() is working in some cases to refresh the UI, then itâs because it is displaying a UI element, the message. The problem I had was that a simple delay does not affect the UI, so it never updates.
I just checked, and no. In my case, a single trigger
None of those involved further triggers.
The effect is the alert popup while the piece is shown after the layer changes. The bookkeeping and the discard happens after the alert is acknowledged.
Ok Thanks Ben.
That has given me another idea to try.
Ok, Found a super hacky solution, but it seems to work.
Added functions
Sleep(ms) to Sleep for a bit. Screen refreshes
Alert(text, ms) to close an Alert Box automatically after a delay.
Test build is the âDelayâ build in Builds of vassalengine/vassal.
First of all I must thank all of you for the answers to my question.
The Brentâs super hacky solution is simply great!
I need to have a delay (with refresh) a) between triggers and b) between groups of triggers within a loop.
Thank you!
Hello everyone,
I recently needed to create an animation to make my dice âroll.â Until now, I was only using a âLayer Traitâ with 2 colours to indicate that the die had been rolled. However, this approach works moderately well with a game that has many dice of different colours.
So, I am sharing with you what I did to create this animation.
Before describing the functionality, here is a list of my requirements:
Firstly, I represent the different faces of my die with a âLayer Traitâ. I have a âNamed Commandâ to increment (âIncrementâ) and another to randomise (âRandomizeâ). The âLevel nameâ must correspond to the displayed face of the die.
The âDiceâ prototype definition has these traits:
There is then a âTrigger Actionâ that provides the user with an option to roll one or more dice. This âTrigger Actionâ will actually initiate these different âKey Commandsâ:
âCheckAndSetGlobalPropertyâ is used in the following âTrigger Actionâ, which checks that the âGlobal Propertyâ âNumberDiceSelectedâ is equal to 0. If this is the case, the âKey Commandâ âSetGlobalPropertyâ is triggered.
âSetGlobalPropertyâ is used in the âSet Global Property Traitâ to set the number of selected dice into âNumberDiceSelectedâ.
In summary: if the user selects multiple dice and triggers the âRollâ action, the number of selected dice is placed in âNumberDiceSelectedâ if it is equal to 0 (which means it has not yet been defined).
Note: I would like to remind you that when the user selects multiple pieces and triggers an action on them, Vassal will call that action on each of the selected pieces.
âDecrementGlobalPropertyâ is used to decrement âNumberDiceSelectedâ (as shown in the âSetGlobalPropertyâ image).
âCheckAndStartLoopâ serves a similar purpose to âCheckAndSetGlobalPropertyâ. It checks if âNumberDiceSelectedâ is equal to 0; if so, it triggers the âKey Commandâ âStartLoopPieceâ.
âStartLoopPieceâ is simply used to trigger the âGlobal Hotkeyâ âStartLoopâ, which will initiate the animation loop.
For each piece selected by the user, the âRollâ action will be triggered. The first piece triggered will set âNumberDiceSelectedâ, and then each subsequent piece will decrement âNumberDiceSelectedâ until the last piece triggers the loop.
Each time âRandomizeâ is called, we will concatenate the âGlobal Propertyâ âRollMessageâ with the âPieceNameâ property that corresponds to the value of the die.
A portion of the logic that enables the animation is defined at the module level.
The âAction Buttonâ âRollâ will be triggered when a user presses it or when âStartLoopâ has been initiated. It will first trigger the âHotkeyâ âLoopStartâ (not to be confused with âStartLoopâ), then it will trigger the âHotkeysâ âLoopâ and âSleepâ 10 times (chosen arbitrarily), and finally, it will trigger the âHotkeyâ âLoopEndâ.
âLoopStartâ is used by a âChange-property Toolbar Buttonâ attached to âRollMessageâ to reset âRollMessageâ.
âLoopâ is used in a âGlobal Key Commandâ that will trigger âIncrementâ on each of the selected dice.
âSleepâ is used in a âGlobal Key Commandâ that will trigger the âGlobal Key Commandâ âSleepPieceâ on a piece that has the âBasic Nameâ âSleepPieceâ. This piece is placed outside the play area (-1000, -1000) and contains a âDynamic Propertyâ âSleepPieceâ that holds the âKey Commandâ âSleepPieceâ, allowing the use of the âSleepâ function for 50 ms (chosen arbitrarily).
âLoopEndâ is used once in a âGlobal Key Commandâ that will trigger âRandomizeâ on each of the selected dice. It is then used a second time in another âGlobal Key Commandâ that will display the result message in the âChat Logâ.
And there you go, it is quite complex, but it works well. Please feel free to let me know if you have any suggestions for improvements!
