I have found a small bug when using duplicate topics (ie using the same topic 2 or more times in the contents window).
When using the auto-browse option from the Project Properties | Common Properties | Browse Sequences dialog, the following problems occur:
In WinHelp, the original topic is included in the browse sequence, but the duplicate topic is not included at all.
In HTML Help, again the original topic is fine, however, the duplicate topic thinks that it is the original topic and continues to browse from the original topic's position (leads to a loop).
How can I get around this?
I know that I can't use a topic in more than one browse sequence, and even if I could, the browse sequencer does not distinguish between original and duplicate topics (maybe it should?)
(Also I'd prefer not to use browse sequences at all, as I prefer the linear approach that auto-browse provides)
Cheers
Sequencing Duplicate Topics
Moderators: Alexander Halser, Tim Green
- Matt Everett
- Posts: 14
- Joined: Tue Jul 23, 2002 4:38 pm
- Location: Cambridgeshire, UK
- Contact:
Sequencing Duplicate Topics
Matt Everett
Technical Specialist
[b]Pico Technology Ltd[/b]
[email]matthew@picotech.com[/email]
Technical Specialist
[b]Pico Technology Ltd[/b]
[email]matthew@picotech.com[/email]
- Alexander Halser
- EC-Software Support
- Posts: 4106
- Joined: Mon Jun 24, 2002 7:24 pm
- Location: Salzburg, Austria
- Contact:
- Matt Everett
- Posts: 14
- Joined: Tue Jul 23, 2002 4:38 pm
- Location: Cambridgeshire, UK
- Contact:
Single Sourcing Improvements
I see what you are saying here, and understand the difficulties
... but I think it would be possible (especially since HM3 is single sourcing) to separate the architecture of HM3 from the architecture of the Help Files (after all, this is what single sourcing is all about).
The concept of having duplicate topics with HM3, is a time saving and continuity enhancing feature (very useful). However, by creating 2 similar topics these benefits are completely removed:
... but I think it would be possible (especially since HM3 is single sourcing) to separate the architecture of HM3 from the architecture of the Help Files (after all, this is what single sourcing is all about).
The concept of having duplicate topics with HM3, is a time saving and continuity enhancing feature (very useful). However, by creating 2 similar topics these benefits are completely removed:
My suggestion would be to find a way of rendering the duplicate topics with different topic IDs in the actual help file (making them entirely separate topics), whilst retaining their linked nature within the .hm3 file (therefore retaining the benfits above).You must create two similar topics if you want to include them in different browse sequences.
Matt Everett
Technical Specialist
[b]Pico Technology Ltd[/b]
[email]matthew@picotech.com[/email]
Technical Specialist
[b]Pico Technology Ltd[/b]
[email]matthew@picotech.com[/email]
- Alexander Halser
- EC-Software Support
- Posts: 4106
- Joined: Mon Jun 24, 2002 7:24 pm
- Location: Salzburg, Austria
- Contact:
This doesn't work, technically. If H&M divided one and the same topic into two different topics, which one should be used if you jump to it?
I don't see much difficulty in separating the topic manually. If you don't want to maintain the topic content twice, use the Embedded Topic function to merge the text.
I don't see much difficulty in separating the topic manually. If you don't want to maintain the topic content twice, use the Embedded Topic function to merge the text.
Alexander Halser
Senior Software Architect, EC Software GmbH
Senior Software Architect, EC Software GmbH