Continuous Monthly Structure
Internally, Q++ calculates a starting date for each diary page it generates.
In a Continuous flow of dates, the date of a token with DayValue of 1 will be 0 days after that starting date. The date for a token with DayValue of 5 will be 4 days after the starting date, and so on. A token with DayValue of 43 represents a date one day later than a token with DayValue of 42.
This may seem obvious but, if you use one of the backtrack settings, that is not the case. Using either of the backtrack settings, a 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 !
In the daily, weekly or yearly grid structures, the flow of dates is always Continuous; it is not an option. Setting the Flow of Dates of a monthly grid to Continuous, is equivalent to telling Q++ not to treat the current grid any differently than daily, weekly or yearly grids.
We have never come across any truly continuous monthly grid. This setting would be necessary when you want total control over the flow of dates in a monthly grid, and do not wish Q++ to make any assumptions about the date of a token given its DayValue. One example that comes to mind is a grid which would present the current and next months every month (ie. page 1 would have Jan-Feb, page 2 : Feb-Mar, page 3 : Mar-Apr, etc…).
Before using this setting, bear in mind that the assumptions that Q++ makes using the backtrack settings are very useful. With total control comes a lot more work. You would probably have to create a GridTemplate for 30-day months and one for 31-day months, if not one for 30-day months that begin on a Monday, one for 30-day months that begin on a Tuesday, … then you would have to assemble many different grids using one DiaryGridLine per month … I think you get the point.