Inside a pipeline that is referenced by "Pipeline executed to capture logging" path variables are displayed incorrectly; plus minor issues

Issue I (main issue):

In a project that uses workflow and pipeline logging, we have a pipeline referenced by "Pipeline executed to capture logging" ("logging_a_pipeline.hpl" in "logging"-subfolder) inside the Metadata object "Pipeline_Log".

The "Pipeline_Log" captures the output of "produce_data.hpl" in "sub"-subfolder.

The pipeline "logging_a_pipeline.hpl" uses two "Text file input" transforms whose paths use variables ("${Internal.Entry.Current.Folder}" or  "${Internal.Pipeline.Filename.Directory}", the problem is the same for both).

The tooltip on the paths in the "Text file input" transforms does NOT show the path that is actually produced when the project runs, and is therefore incorrect (or, at least, very misleading).

The exact symptom is that during execution of the project the variables actually hold the path to "sub" folder that contains "produce_data.hpl", but not (as one would expect and what the tooltip shows!) the path to the "logging" folder that contains "logging_a_pipeline.hpl".

How to reproduce:

simply start "main.hwf", and then experiment with the paths in the "Text file input" transforms in "logging_a_pipeline.hpl".

Issue II (minor):

The documentation on the checkbox "Logging parent pipelines only" in https://hop.apache.org/manual/latest/metadata-types/pipeline-log.html is missing.

I was quite confused about the semantic, but  what I think I could find out is, that in case the checkbox is checked, the log is ONLY produced if the pipeline is started directly. Is that correct?

see

https://hop.apache.org/manual/latest/metadata-types/pipeline-log.html
https://hop.apache.org/manual/latest/metadata-types/workflow-log.html

Issue III (minor):

The paths under "Capture output of the following pipelines" can use variables (here: "${PROJECT_HOME}", but are

• missing the blue diamond symbol which is normally present
• CTRL+SPACE does not work

Issue IV (minor):

The path in "Pipeline executed to capture logging" does not accept CTRL+V