Sigil-0.9.10 Released

[KevinH]

Originally Posted by Notjohn

Has anyone else encountered security warnings when downloading Sigil? I got a bunch, but then I have been testing Brave as an alternative to Chrome. It is perhaps edgier about the web dangers than Google is.

To be safe ...

- please disable or better yet remove any download manager or download speedup adware/malware that mght be present on your machine

- disable any auto launching of downloads in your browser

- download the release ONLY from our github site release page

- BEFORE installing verify the sha 256 checksum (see the checksums text file) to make sure you have an exact copy of what was posted to our github release page.

- if on a Mac you can also use codesign tools to verify my official Apple Developer ID signature on both the dmg file and the Sigil app itself

[Doitsu]

Originally Posted by Notjohn

Has anyone else encountered security warnings when downloading Sigil?

You most likely got the following Windows Defender SmartScreen message:



(Windows Defender SmartScreen checks downloaded files against a list of files that are well known and downloaded by many Windows users. If the file isn't on that list, SmartScreen shows the above message.)

Since the Sigil 0.9.10 installer is a brand-new file, it'll trigger this message, until a large number of users have downloaded the new installers.

As long as you download the installer from the official Github website, you can ignore this message.

[exaltedwombat]

Originally Posted by KevinH

I will try to bring that back for the next release if there is someway to separate a mousepress event in a link area from a mousepress event in a non-link area. Webkit will detect link related clicks (with any and all modifier keys) and send a signal with a URL but the mousepress event itself does not provide info to know if a scroll update is wanted or the beginning of a link click.

Short of that we will add a preference setting for the next release allowing the user to set how they want clicks in Preview to be treated if needed.

KevinH

And that is why we love Sigil! Thank you.

[RbnJrg]

I installed the new version but I can't run it since it appears a dialog saying that the file "api-ms-win-crt-runtime-l1-1-0.dll" is not present. I reinstalled Sigil but the issue remains. ¿What can I do?

EDIT: I'm using Windows 7 64 bits

[ziegmar]

Could someone explain me how to use this useful new feature?

allow plugins to supply their own icon (plugin.png 48x48) for use on the Quick Launch Toolbar icons

Thank you in advance

[Doitsu]

Originally Posted by ziegmar

Could someone explain me how to use this useful new feature?

Select Edit > Preferences > Open Preferences Location.

Double-click the plugins folder then double-click the desired plugin folder and copy the plugin image file to the folder.

For example, you could copy the attached file, which BeckyEbook designed, to the EpubCheck folder.

[RbnJrg]

Originally Posted by RbnJrg

I installed the new version but I can't run it since it appears a dialog saying that the file "api-ms-win-crt-runtime-l1-1-0.dll" is not present. I reinstalled Sigil but the issue remains. ¿What can I do?

EDIT: I'm using Windows 7 64 bits

I think I found the cause of the issue. I had already installed the lasted C++ VS 2015 runtime library. When I installed Sigil 0.9.10, I don't know why, it installed again the Visual C++ Redistributable para Visual Studio 2015. And with that distribution, Sigil didn't run. Then I did the following:

1. I uninstalled Sigil 0.9.10
2. I unistalled MS Visual C++ 2015 Redistributale (x64)
3. I installed again vc_redist.x64.exe
4. I installed again Sigil 0.9.10 and when Sigil wanted to install the C++ runtime library, I aborted the installation and this time, Sigil worked.

It seems that Sigil want to install MS Visual C++ 2015 Redistributale (x64) even when this package is present and updated.

[icallaci]

Originally Posted by exaltedwombat

Bit of a bummer that, when you're using Preview to - well - preview your book, and spot a typo. Given a choice of easily fixing typos and checking links, I'd vote for the typos.

Having jumped to another tab through a link, is there a Back function?

Second vote for the old behavior, although I suppose I'll get used to it. It was much easier to find a particular spot in code view if I could just click on it in preview. Now I guess I'll use Search instead of scanning the preview. Extra typing for me, but oh well. I used to be a software dev so I know compromises are inevitable. I'm not complaining, just voting. And

[icallaci]

Originally Posted by KevinH

I will try to bring that back for the next release if there is someway to separate a mousepress event in a link area from a mousepress event in a non-link area. Webkit will detect link related clicks (with any and all modifier keys) and send a signal with a URL but the mousepress event itself does not provide info to know if a scroll update is wanted or the beginning of a link click.

Short of that we will add a preference setting for the next release allowing the user to set how they want clicks in Preview to be treated if needed.

KevinH

Either one of those would work for me. Thanks!

[ziegmar]

Originally Posted by Doitsu

Select Edit > Preferences > Open Preferences Location.

Double-click the plugins folder then double-click the desired plugin folder and copy the plugin image file to the folder.

For example, you could copy the attached file, which BeckyEbook designed, to the EpubCheck folder.

Thank you!
The trick was to name the plugin.png icon file regardless of the plugin we're dealing with.

[DiapDealer]

Originally Posted by RbnJrg

I think I found the cause of the issue. I had already installed the lasted C++ VS 2015 runtime library. When I installed Sigil 0.9.10, I don't know why, it installed again the Visual C++ Redistributable para Visual Studio 2015. And with that distribution, Sigil didn't run. Then I did the following:

1. I uninstalled Sigil 0.9.10
2. I unistalled MS Visual C++ 2015 Redistributale (x64)
3. I installed again vc_redist.x64.exe
4. I installed again Sigil 0.9.10 and when Sigil wanted to install the C++ runtime library, I aborted the installation and this time, Sigil worked.

It seems that Sigil want to install MS Visual C++ 2015 Redistributale (x64) even when this package is present and updated.

I'll look into it. But Sigil is only supposed to install the runtime if a) there is no VS2015 runtime installed, or b) an older version than the one included with Sigil is installed. Perhaps something has changed regarding how Windows indicates if--and what version--is installed.

[BetterRed]

Originally Posted by icallaci

Second vote for the old behavior, although I suppose I'll get used to it. It was much easier to find a particular spot in code view if I could just click on it in preview. Now I guess I'll use Search instead of scanning the preview. Extra typing for me, but oh well. I used to be a software dev so I know compromises are inevitable. I'm not complaining, just voting. And

Could a modified left click (e.g. Ctrl+Click) be used, optionally perhaps, for Go to link.

BR

[KevinH]

Originally Posted by BetterRed

Could a modified left click (e.g. Ctrl+Click) be used, optionally perhaps, for Go to link.

BR

Unfortunately, the modifier key (any of them) do not change how webkit signals a link has been clicked.

[BetterRed]

Windows : Can I install 32 bit 0.9.10 alongside 64 bit 0.9.9 ? And use both, obviously not at same time on the same epub.

Will I have issues with C++ re-destructible libraries ?

BR

[DiapDealer]

Originally Posted by BetterRed

Windows : Can I install 32 bit 0.9.10 alongside 64 bit 0.9.9 ? And use both, obviously not at same time on the same epub.

Will I have issues with C++ re-destructible libraries ?

BR

Not really sure, to be honest. My gut says no (no there shouldn't be any issues), but Windows is so weird about how memory-resident functions of dlls work/persist, that I wouldn't swear to it. The sigil-specific dlls (python35 gumbo and hunspell) shouldn't cause any issues. Because 1) they've not been altered between 0.9.9 and 0.9.10; 2) they were all built with VS2015; and 3) Windows first priority for library search paths is the current directory (so all of those libraries are packaged adjacent to the Sigil executable for that exact purpose). The environment for the python-based plugins (run in a separately executed process) is tightly-controlled and should pose no problems.

Just remember they'll share the same preferences unless you launch one version of Sigil with the SIGIL_PREFS_DIR set to somewhere else.