Thanks for clarifying that.

From what I recall working with the code this is expected behavior. The record flag is set on a chain of tracks within a page, meaning that you can have multiple pages set to record at the same time. There is a concept of a GRID_CURSOR which decides which page to record into. This is always the page that is currently selected. You can try a quick experiment in Grid View and select another page. I would expect that recording to the previous page would no longer work. I think the reason for this behavior is to support page follow recording with page clusters. There are also some references in the code to a "book" that seems to have been used as a reference for the data structures, so this may have been inherited from learnings made from older machines.

I'm trying to record into a page while viewing another page. I have set the track to arm and engaged record and it all works fine if I'm in that page or up one level in GRID mode, but if I then go into another page the Octopus never records. Is this expected behaviour or have I just missed something really obvious? I've been at it for an hour now and I might just be suffering from task blindness..