@Chris
Quote:
AmigaGuide has a big advantage that amigaguide.library allows programs to open help files at a contextually useful node.
One thing I don't like about the AmigaGuide Library is the fact that the AmigaGuide context you initialize is tied to a particular screen. This is very inconvenient now that programs can travel between screens, thanks to the screen jumping feature in the Window Class. So with every screen change you need to dispose of the AmigaGuide context and re-establish it in reference to the new screen.
A possible approach is what I have done in my AmigaGuide Class (I think you've seen the code), which hides the library internals behind the BOOPSI wall and makes your help file happily oblivious of the screen it's going to open on. I might revisit the class code if there's interest and if OS4 development gets back on track after all the legal mess.