Timer supersedes on other timer on different page

[yaslena]

Some elements of this issue have been described in #116 and #120 but because this problem exists independently of other problems with page transitions and page criteria I will describe it in a separate issue here:

Problem: One timer on one page can supersede on another timer on another page.

For example when you have a timer of 30sec on page A and another timer of 30sec on the next page B (like in managing lunacy 4.5.15a and 4.5.15b), then the following happens:

• The second timer will be displayed as 0 when you come to page B and the timer on page A has already expired.

• If the timer on page A has not yet expired and you move to page B when the first timer is still running, than the timer from page A will continue running on page B. This means that when you come to page B, the timer will not start off with the 30sec that have been set for this page, but with the remainder of the time from page A.

The problem always occurs when a storyline has consecutive pages with timers or when a player switches between storylines quickly and opens several pages which have a timer after another.

When a player quickly switches between storylines that have timers, a similar phenomenon can be observed:
When you play Plantation Lives until the first page with a timer (2.1.3; 3min) and then go back to game selection and switch to another game that also has a timer (like trailer "lit-demo" page 1.1.7.1.2; 5min) while the timer in Plantation Lives has not yet expired then the following happens: When you get to the second page that has a timer, the remaining time of the first timer will be displayed. So, in the trailer you will not start off with 5min, but with 1min or 2min depending on how quickly you left Plantation Lives and got through the first pages of the Trailer.

[martindusinberre]

@Helena-LiT Many thanks for spotting this and opening an issue. This may explain some of the occasionally odd timer experiences I have, which I have never been able to reproduce.

[interrogator]

@Helena-LiT yes, many thanks for describing this one! Note that a fix will not be available in the current release, and there is no planned/funded future development cycle, so it is best to just use workarounds for this where possible.