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

3 replies
146 views
Translate

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

Jeff_CoatsworthCorrect answer

Community Expert

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

Jeff_Coatsworth

Correct answer

Community Expert

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

Translate

oliviert5031601Author

Inspiring

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

Translate

Jeff_Coatsworth

Community Expert

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.

Translate

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.