Browse sequence

[sthi]

Hello,

is it possible to implement a browse sequence like this:?



Currently my browse sequence is located within the toc at the lower part, but in general a browse sequence should be located above the topic content (like in the picture). Is this possible?

Greets,
Stefan

[RamonS]

Welcome to the forums!
From what I recall the Flare browse sequence is really just an addition to the ToC. It is not a real browse sequence that specifies a fixed path of progression through topics with a definitive start and end. Way back I asked for this, but have abandoned using CHM quite a while back (and to be honest, tech writing is now more a hobby for me).
That said, maybe someone has a suggestion, but I wouldn't count on it. You may need to look into using tools to implement real browse sequences...assuming that they are still available in HTML Help 1.4. I looked through the documentation and cannot find anything for browse sequences.
The example that you showed, do you know with which tool was that created?

[Nita Beck]

Flare does support a browse sequence, but implements it in a different way, as Ramon said, as a sort of second or alternative TOC. The screenshot above shows how RoboHelp implements a browse sequence. So the short answer is, no, you can't get RoboHelp's implementation out of Flare.

[sthi]

Thank you all for the quick response!

Yes, the screenshot is from a Robohelp output.
I tested it a few month ago in Robohelp and I thought (and hoped) the browse sequence will be the same in Flare.

Perhaps I will find a solution, because the bs within the toc isn't really an alternative for us.

Greets
Stefan

[RamonS]

You are not alone. You can put in a feature request here:
https://www.madcapsoftware.com/feedback ... quest.aspx

Not sure why MadCap opted for the rather light and not very useful implementation of browse sequences through the ToC. It does make use of means available in all targets which makes single sourced outputs more consistent, but I did miss the RoboHelp style browse sequences. Maybe Adobe has a patent on that?