Backtrack every Page Monthly Structure
As its name indicates, the Backtrack Every Page setting is related to Backtrack Every Month. If you use the present setting Q++ will also assume that the grid has an underlying structure of 42 days month blocks.
When a new page of the GridTemplate is encountered, Q++ looks at it minimum DayValue, divides it by 42 and decides that the minimum date is that number of months later than the previous page. For example a 4 months on 2 pages grid has tokens beginning with DayValue of 1 on the left and DayValue of 85 (one more than 2 times 42) on the right. Therefore Q++ assumes that the right page contains dates that are 2 months later than the left page.
That in itself is not different than the DayValues we would use for a Backtrack Every Month grid. The difference comes from the fact that within a page of the grid, Q++ makes no attempt at interpreting the DayValues (ie. it treats the flow of dates within each page, as continuous).
In the case of a Backtrack Every Page grid, the date of a token of DayValue of 42 will be one day less than that for a token of DayValueof 43, as long as the 2 tokens are on the same page. This is in contrast with a Backtrack Every Month setting for which token with DayValue of 42 can actually represent a later date than a token with DayValue of 43, sometimes by as much as 13 days !
Finally, note the effect of setting the option Outside Days to hide in "Grid Options"; the only days that are hidden are the days prior to the first month of the page, and days after the last month of the page.
Sample : 4 months on 2 pages, backtrack every page, first date = week of the first.