Skip to main content
oliviert5031601
oliviert5031601
Inspiring
November 18, 2025
Answered

RH2019 classic CHM after changes in source and subsequent generation, output view is not modified

  • November 18, 2025
  • 1 reply
  • 44 views

I do this 3 times, for 3 languages.

modify, compile and launch view example

for one of the three project, the modifications are not shown, the two others are ok.

generate options are identic, path also...

even if I erase the old target file, it is still showing a wrong result.

if added a printscreen with the source and the result.

I'm baffled

br Olivier

    Correct answer Jeff_Coatsworth

    How are you viewing the output? Have you generated the CHM to a different location and tried opening it from there?

    1 reply

    Jeff_Coatsworth
    Community Expert
    Jeff_CoatsworthCommunity ExpertCorrect answer
    Community Expert
    November 18, 2025

    How are you viewing the output? Have you generated the CHM to a different location and tried opening it from there?

    oliviert5031601
    oliviert5031601Author
    Inspiring
    November 20, 2025

    Hello Jeff,

     i'm viewing output. tried both solutions

    1.save and generate and at the end click on 'view result'

    2. navigate to target dir, open chm file.

    I also renamed the shown old chm file (AanDeSlag02OLD.chm)

    RH2019 wrote a 'new' version besides it, curiously with an old date. 

    So somewhere RH is not using the freshly compiled version but write an old compiled version.

    So I started looking in the project file dir tree for old versions. And found one in the root of the project dir.

    Renamed it. And now it's ok.

    A mystery to me!

    And I also don't know why an old version is postionned in the root of the project dir. Historically, or wrong proces step. You don't need your own chm in the root for referral (all bagagefiles are also in the root)

    I suspect this is a bug

    I'll mark it as solved

    br

     

     

     

    Jeff_Coatsworth
    Community Expert
    Jeff_CoatsworthCommunity Expert
    Community Expert
    November 20, 2025

    I don't think it's a bug - it sounds like you've got something messed up in your project folder structure. IIRC RH2019 Classic still uses the \!SSL!\ sub-folder in the project to generate output in. It clears the contents of the specified output type folder first before creating new output. The fact that you were able to rename an existing CHM & not have it blown away means that your SSL recipe is not pointing to the location you think it is.

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices