The goto last visited page only works as long as you DONT do any other other goto actions on the CURRENT PAGE. For example, we do accessibility programming and we have a Skip to Main Content and a main content placeholder on our pages. The Skip to Main Content has a action on it like, On Mouse Click, Go To, Current Page, Scroll to, main content placeholder, Open in Existing Window. Now, if a user uses the Skip to Main Content link on the current page, and then hits the Back Button, it DOES NOT go back to the Last Visited Page, but stays on the same page, because the Last Visited Page command in the publish to HTML only keeps the history of the browser and backs up the browser to the previous command, which, in this case, is still the same page. So, the term “Last Visited Page” that Lectora uses is not exactly technically correct and can be misleading in certain situations like I just described.
We just have found it safer to just do the work and set the actions of the Back button appropriately, either to Go To Previous Page OR … if we do branching etc, disinherit, inherit and change the action to GoTo PageXXX as necessary…
I have a similar problem with the “go to the last page” option. Basically, I designed the course to have a Glossary in a separate chapter, if the user goes to the Glossary, the course takes him to the first page of the chapter (Glossary) and then he have to navigate through the topics. My problem is that I put a button called “Go Back to content”, but basically I need that the “Go back” takes the user to the topic he was reading.
How can I do that?… Is it possible to save n number of positions for a button?