Posted by Alexander Halser in HelpXplain, Software Updates, Uncategorized on October 29, 2020
As part of our commitment to continuous improvement, we’ve released an updated version of HelpXplain. If your maintenance plan for HelpXplain includes the release date (Oct 29, 2020), this is a free update. The quickest way to find out, is to start HelpXplain and click Help > Check for Update.
Version 1.4 comes with 2 new features important for social media sharing. It introduces a setting for custom meta tags. Some users have requested we should add additional social media meta tags (such as a Facebook App_Id). The new meta option enables this and a lot more.

The second new feature is in the Publish dialog: an option to mask the viewport of the Xplain. When an Xplain is embedded in another HTML page, the host page normally restricts the viewport so that the view matches the aspect ratio of the Xplain.
Social media sharing, however, often include direct backlinks to the Xplain HTML page directly. In this case, the Xplain runs in a new window or tab of the browser and the window size hardly ever reflects the aspect ratio of the presentation. As a result, some of the slides might become prematurely visible. The mask viewport option blacks out the browser window area which does not belong to the viewport.

The difference between masked and unmasked viewport explained:
Other changes and bug fixes in version 1.4:
This update is included in your maintenance plan! Please download the update and install it over your existing version.
Posted by Alexander Halser in Uncategorized on August 18, 2020
We have received several complaints between July 11th and today from people who have been charged (on their bank account or their credit card) in the name of “helpandmanuals.com“. (Note the “s” at the end of the domain name, which is different from our domain, which is “helpandmanual.com“). Does this apply in your case? Read the rest of this entry »
Posted by tim green in Uncategorized on February 26, 2020

If you are using eWriter books as documentation for your software you will want to open specific topics in the help from your application. To do that you need to be able to reference the viewer directly, so it is best to install it along with your software. You can’t be sure that the user will have it or where it will be otherwise. You also need to consider the following issues:
Read on to learn how to get this set up and working optimally.
The current version of eViewer.exe is always included in the Help+Manual program directory. You just need to include it in your own installation. It doesn’t require any special installation or registry keys. It will actually run fine from a USB stick. If you wish you can rename the viewer file and re-sign it with your own certificate so that it matches the rest of your software. That is entirely up to you and we don’t have a problem with it.
We also recommend that you do not register the .ewriter extension as part of your installation. Instead, always make your calls explicitly to your installed eViewer.exe and your own help files. This guarantees that you are using the same viewer that was up to date when you generated your help. However, you will also want your users to be able to open your help files themselves by double-clicking on them. So read on to learn how to do that.
It is also fine and actually a good idea to change the extension of your help files to anything you like. If you do this, you can register your own custom extension to your installed version of the eViewer application so that your users can open your help files themselves by double-clicking on them.
Then you don’t get any conflicts if the user gets .ewriter files from somewhere else. If they open .ewriter files on Windows 10 they will get the Windows Store version of eViewer automatically (and that extension is required for the Store viewer), and then you don’t have any conflicts: The .ewriter extension is always used for the Store version and your application always opens your help files with your installed version of the viewer.