I have a large form spanning over many pages which is flowable - so it can grow in size depending on the data inputted. Because of this I have managed to create buttons which can print sections rather than page numbers, which works well. because of the size of the form, I have placed all these print buttons on one page at the end of the form - think of it as a table of contents with buttons instead of page numbers if that makes sense. I'll call this the 'printing section'
The problem with this however, is that if the user goes to the 'printing section' to print a certain section they may get lost so I need to create a button that will send then back to the last page they viewed. this could be page 20 or page 40 or whatever, it just depends on where they were before they clicked the button that sent them to the 'printing section'.
I think I get where you're coming from. The issue I have is that I don't want a print button to appear within the body of the form (as it can, and does, expand dramatically when the user enters text into the fields). My initial solution was to put a print icon in the footer of each master page (each master page is a section of the form, and there are about 8 of these sections). In doing this I can reference a go back to section button in the 'printing section' but I think the best I could do would be to go to the start of the previous section rather than a particular page.
I could be wrong here, so do let me know!
Another solution I thought of would be some kind of code (alas I'm learning here, so bear with me) that, in plain english was attached to the print button that said before going to the 'printing section' make a note of the last text field/button etc. to be clicked into and then have the back button set focus and return to this. It's not perfect as there is a possibility that the user didn't click into anything.
I guess what I was hoping for was that as you scroll through the pages you can see the page number change through acrobat's main window. So in my head I was thinking would there be a way on the fly to monitor this and for the coding to effectively go back to the last page number visited prior to the user going to the 'printer section'.