Help & Manual Forums

Alexander Halser wrote:The problem has been fixed with Help+Manual Build 4434:
https://www.helpandmanual.com/downloads.html

Thank you! I also just verified it is fixed in Build 4434.

I will say again to the H&M developers: please have the WebHelp export not resize images from their original resolutions when em units are specified in the preferences. I agree with mmccullo there should be an option to allow the same thing for Webhelp output, i.e. the original png, gif or jpeg...

I've provided an example HTML page that makes it clear you can use higher pixel count images with em scaling and the result is a better (sharper) image on higher pixel density displays because the additional pixels are rendered in the same physical space on screen. Can you not see the difference? Tr...

No, no, no. See: http://www.cssplay.co.uk/menu/em_images Em scaling can scale any pixel count and use the local display density to render more detail when available. By specifying 50% scaling in the H&M editor, I am not asking the WebHelp export to reduce the pixel count! It appears when I selec...

If I want to scale an imported image in the H&M editor, I don't want the WebHelp export to change the original pixel count for ANY given scaling, not just 99.90%. Let the browser image rendering take care of that on the local display, whatever the DPI or scaling or whatever you want to call it. ...

But that is not what I want at all. I will try to explain again. I do my image captures at 200% Win 10 scaling on a 4K monitor. That means the relative physical sizing of elements on-screen is identical to a same-sized monitor running at 100% at 1920 x 1080 resolution. So when i do a screen capture,...

Ok since you didn't like the way I phrased it... I want WebHelp to export my image unchanged from the captured pixel dimensions with a scaling factor other than 100%. Why do I have to specify the scaling as 100% (or 99.90%) when modern browsers can scale down large images just fine and use the extra...

I work on a 4K screen and save my screenshots as 192 DPI images (200% scaling) in PNG format. These display fine in the H&M editor and I specify a scaling factor to size them appropriately. When I run WebHelp, it wants to convert all images to 96 DPI at the scaled size. This results in the scale...

This is reported for version 7.32. I also checked the installer and Windows Defender is still reporting the trojan detection in the installer file.

So... I uploaded it to VirusTotal.com and checked it. Nothing is reported as detected. ???

Windows Defender just reported detection of this trojan. Has anyone else experienced this? Is this a known false detection?

Do the TOC sync bug noted for Safari and Chrome get a workaround in the standard version skins?

I have the standard version of H&M v5.5 (and the 3 standard HMSkins) and find that neither Chrome nor the UIWebView object in iOS 4.2 will open folders or sync the TOC frame.

---
Michael McCulloch