Sigil-2.0.1 Released

[DiapDealer]

Sigil-2.0.1

Sigil 2.0.1 represents a bug-fix only release.

Bug Fixes

• fix crash when right click on Misc folder in BookBrowser
• Allow user to revert CodeView drag_and_drop change via environment variable: SIGIL_ALLOW_CODEVIEW_DROP=1
  
  Note: Using DragnDrop in CodeView is still NOT officially supported.
  
• add inadvertantly missed updated Serbian translation (ts) file

--------------------------------- Notes -----------------------------------

The latest version of the Sigil User Guide can always be downloaded from the Sigil website, or from its own GitHub repository.

Please check the Sigil website for important Sigil support links, additional resource downloads, and platform-specific trouble-shooting tips/requirements.

The MacOS builds are signed but they are NOT notarized. See this PageEdit/Sigil issue for more information.

PGP Fingerprint (for signed tags and source archives):

B5A5 6206 AB0F BC1A 24EF AB8A A166 D29A 8FCD AC63

All Sigil binary (and source) downloads can also be found as assets at the bottom of The Sigil-2.0.1 Github Release page.

[DiapDealer]

Reserved for future use

[diego77]

Sigil 2.0.1
OS X (Monterey)

“Sigil” cannot be opened because the developer cannot be verified.

[Turtle91]

This is a known issue because it is WAY TOO EXPENSIVE to pay Apple their extortionist rates to 'get certified'.

There is a checksum on the downloads page you can use to verify - always use the downloads page, not some 3rd party site - then use the 'continue anyway' options.

[diego77]

Solved with this in Terminal:

xattr -cr (app path)



EDIT: I'm sorry! I've missed the open twice
Thanks KevinH

[KevinH]

Originally Posted by diego77

Sigil 2.0.1
OS X (Monterey)

“Sigil” cannot be opened because the developer cannot be verified.

Please at least read the Release Notes above. It explicitly addresses this issue in the following quote:

The MacOS builds are signed but they are NOT notarized. See this PageEdit/Sigil issue for more information.

There is no need to clear the quarantine attribute. Just right click on the app and select open twice in a row. Sigil will launch.

[galax]

Greets,

Quick question, does Sigil 2.0.1-r2 work with qtwebengine 'vulkan' only? Or does it rely on 'opengl'?

thanks.

[galax]

Warning: QGuiApplication::setDesktopFileName: the specified desktop file name ends with .desktop. For compatibility reasons, the .desktop suffix will be removed. Please specify a desktop file name without .desktop suffix
Debug: attempted to load a non-existent dictionary:  "en_US"
Debug: vkDebug: Could not open device /dev/dri/renderD128: Permission denied (VK_ERROR_INCOMPATIBLE_DRIVER)
Debug: vkDebug: setup_loader_term_phys_devs:  Failed to detect any valid GPUs in the current config
Warning: No physical devices
Warning: Failed to create QRhi for QBackingStoreRhiSupport
Debug: vkDebug: setup_loader_term_phys_devs:  Failed to detect any valid GPUs in the current config
Warning: No physical devices
Warning: Failed to create QRhi for QBackingStoreRhiSupport
Warning: QQuickWidget: Failed to get a QRhi from the top-level widget's window
Warning: QQuickWidget::resizeEvent() no QRhi
Debug: vkDebug: setup_loader_term_phys_devs:  Failed to detect any valid GPUs in the current config
Warning: No physical devices
Warning: Failed to create QRhi for QBackingStoreRhiSupport
Warning: QQuickWidget: Failed to get a QRhi from the top-level widget's window
Debug: vkDebug: setup_loader_term_phys_devs:  Failed to detect any valid GPUs in the current config
Warning: No physical devices
Warning: Failed to create QRhi for QBackingStoreRhiSupport
Warning: QQuickWidget: Failed to get a QRhi from the top-level widget's window
Warning: QQuickWidget::resizeEvent() no QRhi
Warning: QQuickWidget: Attempted to render scene with no rhi
Segmentation fault

[galax]

Fixed, user needed to be in the 'render' group.

[DiapDealer]

Moved your last posts to the the 2.0.1 release thread.

I'm unfamiliar with the Sigil 2.0.1-r2 version. Is that a package from a particular distro? If so, which one? I ask because this is the first I've heard of users needing to be manually added to the system 'video' or 'render' group in order to run Sigil. Especially when using a distro-provided package.

[democrite]

Since I remembered such now, I thought I might mention. A small detail. Once I believe I accidentally clicked remove all plugins. Oh my. Perhaps such should have a confirmation? I recall it doesn't but maybe it does. As I don't recall seeing such a button on other apps perhaps the idea of remove all itself isn't so great and the button doesn't need to be there?

[KevinH]

There is already a confirmation MessageBox when you try to remove all plugins.
It works on my mac just now. If your mac skips it, then that is a bug in Qt 6.5.2 that is fixed in Qt 6.5.3

void PluginWidget::removeAllPlugins()
{
    PluginDB *pdb = PluginDB::instance();
    QMessageBox msgBox;

    msgBox.setIcon(QMessageBox::Warning);
    msgBox.setWindowFlags(Qt::Window | Qt::WindowStaysOnTopHint);
    msgBox.setWindowTitle(tr("Remove All Plugins"));
    msgBox.setText(tr("Are you sure sure you want to remove all of your plugins?"));
    QPushButton *yesButton = msgBox.addButton(QMessageBox::Yes);
    QPushButton *noButton  = msgBox.addButton(QMessageBox::No);
    msgBox.setDefaultButton(noButton);
    msgBox.exec();
    if (msgBox.clickedButton() == yesButton) {
        ui.pluginTable->setSortingEnabled(false);
        while (ui.pluginTable->rowCount() > 0) {
            ui.pluginTable->removeRow(0);
        }
        pdb->remove_all_plugins();
        ui.pluginTable->resizeColumnsToContents();
        ui.pluginTable->setSortingEnabled(true);
    }
    foreach(QComboBox* cb, m_qlcbxs) {
        cb->clear();
        cb->setCurrentIndex(-1);
    }
}

[DiapDealer]

Originally Posted by democrite

Oh my. Perhaps such should have a confirmation? I recall it doesn't but maybe it does. As I don't recall seeing such a button on other apps perhaps the idea of remove all itself isn't so great and the button doesn't need to be there?

There is a request for confirmation if you attempt to remove all plugins. It will suffice, and it will remain as it is. "Other apps don't..." is not really a convincing argument for feature removal. Use it or don't.

[jugaor]

Hello.

Sigil 2 saves .ini files as UTF-8, which is an advantage.
However, now it also exports them with this encoding, which makes it tricky to import them in previous versions if they have special characters (as it happens in languages like Spanish, French, etc.).
This change prevents the correct exchange of "Clips" and "Saved searches" between installations or users (especially now that Windows 7 is no longer supported).
Would it be possible to allow the previous export (ANSI)? Maybe as an additional option?

Thank you very much for your great work!

[KevinH]

Sigil has always used ini format and not utf-8. We once tried utf-8 years ago, and utf-8 files caused numerous issues so we had to revert to standard ini files.

Sigil-2.0.1 still uses normal ini files but for safety to prevent compatibility problems from Qt5 to Qt6 it takes Qt5 generated ini files on first launch and creates Qt6 versions from them.

They are still cross-platform, just using a new name. Once those exist they are used from then on out.

You can of course delete those Qt6 ini files and copy in Qt5 ini files from a previous version of Sigil (1.x) and they will be properly converted to Qt6 ini files when Sigil is next launched.

The old Qt5 names are:

#define CLIPS_SETTINGS_FILE "sigil_clips.ini"
#define INDEX_SETTINGS_FILE "sigil_index.ini"
#define SEARCHES_SETTINGS_FILE "sigil_searches.ini"
#define SEARCHES_V2_SETTINGS_FILE "sigil_searches_v2.ini"
#define SIGIL_SETTINGS_FILE "sigil.ini"

The new Qt6 ini file names are:

#define CLIPS_V6_SETTINGS_FILE "sigil_clips_v6.ini"
#define INDEX_V6_SETTINGS_FILE "sigil_index_v6.ini"
#define SEARCHES_V6_SETTINGS_FILE "sigil_searches_v6.ini"
#define SIGIL_V6_SETTINGS_FILE "sigil_v6.ini"

So which ini files (exact file names and paths) are you talking about?