How do I get a Up One Level in the Topics page of my screen layout?

[VoiceMetrixCorp]

I am trying to insert an "Up One Screen" on my Topic page in my screen layouts and it's only allowing me to add a hyperlink to the Table of Contents. Any suggestions?

[Peter Grainge]

What do you mean by Up One Screen? Where is Rh only allowing you to add a hyperlink to the TOC?

What sort of help are you generating?

What version of Rh are you using?

---

See www.grainge.org for RoboHelp and Authoring tips

@petergrainge

[VoiceMetrixCorp]

I'm using RoboHelp 10. While trying to generate Multiscreen HTML5, it will not allow me to edit the Topic page in the Screen Layouts (Project Set-up pod) to insert an Up One Screen (or a "Back" button which will return users to the previous page). If I add a graphic (like a back button) to the Topics page, it will only allow me to insert a hyperlink back to the Table of Contents (my TOC is broken apart via chapters and I'd like the Topic page to go back to the chapter page as opposed to all the way back to the main TOC). When I attempt to copy and paste the Up On Level (or back button) from the TOC page into the Topics page, I get an error box saying either "The Up One Level cannot be included in the Text box (div)" or "The Up One Level cannot be included in the Cell."

So how do I apply the same attributes that are on the Up One Level box in the TOC to an inserted graphic on the Topics page?

[Peter Grainge]

I have moved this thread to the Multiscreen HTML5 forum.

---

See www.grainge.org for RoboHelp and Authoring tips

@petergrainge

[Guest]

Hi,

I am not sure whether this is what you exactly need, but if you want to use the HTML5 output in the browser then you can just add a hyperlink using the history.back(); function. If you want it to work as a mobile app then add the cordova script and use the navigator.app.backHistory() function.

Just an example, this div carries the top right header part of a layout and includes two buttons; one calls a separate search page (I did away with the permanent search field at the top) and another calls the mentioned back function. The css cares about the layout (display buttons, placement of div).

<div class="headerr">

<a id="btn_suche" class="button" href="Search.slp"></a> <a id="btn_xit"

  class="button" href="javascript:navigator.app.exitApp()"></a>

</div>

[Willam van Weelden]

Hi,

As of now, I don't know any way to return to the TOC with the correct book opened. The mobile TOC uses id's to open the correct book, but id's are assigned on generation. (While it may be possible to retreive the id be writing your own custom widget, I do not think this is feasible. It will take an incredible amount of work and may likely cause performance issues.)

This clearly is a limitation of the widget. For instance, if you add the widget to a topic page, the widget will not work in your output. You may want to submit this idea as a feature request: https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform

Greet,

Willam