Sigil-0.9.16 Released

[Mister L]

Originally Posted by DiapDealer

All toolbar arrangements and widget placement should be restored when re-launching Sigil. Just know that if you have multiple instances of Sigil open simultaneously, the last configuration of the last instance closed is going to be the one that's saved. All of the toolbar/widget settings are saved/restored from the Sigil.ini file.

That's what I thought, and I swear it wasn't working last night and earlier today but it did just now when I tested it, so my apologies and forget I mentioned it.

[BetterRed]

Originally Posted by DiapDealer

I've found that with Sigil and PageEdit, changing the inspector theme will work regardless of any errors that are produced. The change just won't take effect until Inspector is relaunched (or in the case of PageEdit; until PageEdit itself is relaunched).

Why each of those inspector errors are being intercepted by Sigil's own inherent error dialog system is something we'll have to look into. But either way, you should be able to use the dark theme by dismissing all the errors in Sigil and closing/relaunching inspector. In PageEdit, you'll need to relaunch PageEdit entirely for the theme change to take effect.

This is all on Windows, by the way. I've not tested on other platforms.

- thanks for confirming.

After persevering with clicking buttons (which you know I hate) and restarting (Sigil & Page Edit) I managed to enforce the Dark theme on the Inspector gadget in both - and it sticks in both

Can you consider making the Inspector dockable in Sigil, or putting it back where it was - affixed to the Preview window. I don't like windows that I can't park somewhere. Attached is a screen shot of where I have it in Page View.

I ought to mention why I tried the Dark theme. I was looking for a way to increase the Inspector's font size. When nothing leapt out at me I thought I'd try the Dark theme and…. But now I have it working, I do find it much easier to read. But it leaves the question - is there a way to increase the Inspector's font size. Where are the Inspector's Settings stored ?

I have SIGIL_PREFS_DIR=C:\_AppData\Sigil\Prefs, could you add something to PageEdit to use that or a similar EnvVar.

No urgency about any of that.

BR

[DiapDealer]

Originally Posted by BetterRed

Can you consider making the Inspector dockable in Sigil, or putting it back where it was - affixed to the Preview window. I don't like windows that I can't park somewhere.

Making the Inspector a floating widget that can be toggled on and off was a conscious decision. We're not likely to put it back the way it was.

[BetterRed]

Originally Posted by DiapDealer

Making the Inspector a floating widget that can be toggled on and off was a conscious decision. We're not likely to put it back the way it was.

I think I understand why, the presence of the splitter bar wasn't obvious. Making it dockable is my first preference. But I will make more use of it in Page Edit - as a 'Code Preview'.

BR

[DiapDealer]

Originally Posted by BetterRed

I think I understand why, the presence of the splitter bar wasn't obvious. Making it dockable is my first preference. But I will make more use of it in Page Edit - as a 'Code Preview'.

BR

That was a big part of it, yes. It's also a fact that Inspector is just not going to get used as much, as often, in Sigil proper--what with Code View being right there at all times. So rather than take up more space in dock-areas that are already getting quite cluttered, the idea was to fire it up when needed, and then just leave it turned off the rest of the time. Off in this case meaning disconnected and using no resources at all.

[rdean30]

Originally Posted by lwalper

Yep, that's why I'm staying with 9.14. Tried the newfangled PageEdit - didn't like it.

Looks like this project is going backwards. It's like we've lost functionality. The tabbed interface was better, for writing books. Which I thought was the design of the program.

[DiapDealer]

Originally Posted by rdean30

Looks like this project is going backwards. It's like we've lost functionality. The tabbed interface was better, for writing books. Which I thought was the design of the program.

You're entitled to your opinion (though the notion that we got rid of the tabbed interface is quite wrong). I myself feel like we've gotten rid of a dead anchor that's been holding back a lot of future development/improvement

Sigil was never intended for authors to use to "write books." There's tons of software out there that's better suited for that job. It was intended to be used to create and edit epubs. But if you want to use Sigil to write books in Book View, then have at it. No one's stopping you. You don't have to "go backwards" with us. You can stay with the version of Sigil you're most comfortable with forever if you like. I mean, if what you're using is already everything you want it to be, why would you want to upgrade to the latest version anyway?

I find the notion that those who like using Book View have somehow "lost" that functionality very, very confusing. You haven't lost anything. We didn't come to your house and uninstall the version of Sigil that works for you. Keep on using it. Grab a copy of the installer for that version and hang onto it.

[Turtle91]

^^^^+1

Plus - all you have to do is click the button for PageEdit to get the functionality you had before....that's only 1 button click instead of the previous 2 to switch to book view. Sooooo...they have actually cut the amount of work in half!!

[odamizu]

Originally Posted by DiapDealer

... I find the notion that those who like using Book View have somehow "lost" that functionality very, very confusing. You haven't lost anything. We didn't come to your house and uninstall the version of Sigil that works for you. Keep on using it. Grab a copy of the installer for that version and hang onto it.

This ↑ ↑ ↑ a thousand times.

I have an old html editor that I love. When the developer took v3.0 in a direction that didn't suit me, I continued using v2.0 — and that was over 15 years ago. It still works, even though the developer has long since closed up shop (thankfully I saved the installer).

[st_albert]

Originally Posted by odamizu

I have an old html editor that I love. When the developer took v3.0 in a direction that didn't suit me, I continued using v2.0 — and that was over 15 years ago. It still works, even though the developer has long since closed up shop (thankfully I saved the installer).

Off topic, I know, but I have to ask: Arachnophilia, perhaps?

Albert

[odamizu]

Originally Posted by st_albert

Off topic, I know, but I have to ask: Arachnophilia, perhaps?

Taco! However, I'm transitioning my brain to BBEdit in preparation for the macOS 32-bit apocalypse. Though I will probably cling to High Sierra for as long as I can — another example of sticking to software that works for me when the developers head in a direction that doesn't suit me.

That said, I jump on Sigil updates, usually on release day. I just hope Apple doesn't make a mess of the notarization requirement such that development of Sigil for Mac stops.

[patrik]

Hmm, now clicking in the preview window no longer moves the codeview to match. Didn't that get re-installed in .15 (or so)?

[BetterRed]

Originally Posted by patrik

Hmm, now clicking in the preview window no longer moves the codeview to match. Didn't that get re-installed in .15 (or so)?

Sigil 0.9.16 is working fine here on Windows 10 64 bit 1809.

For me that feature has been working fine since 0.9.13. I know this because I held off updating Sigil for a couple of releases while awaiting that fix.

BR

[patrik]

Originally Posted by BetterRed

Sigil 0.9.16 is working fine here on Windows 10 64 bit 1809.

For me that feature has been working fine since 0.9.13. I know this because I held off updating Sigil for a couple of releases while awaiting that fix.

BR

Interesting, could this be a linux-thing?

Yeah, it's very useful and I was also happy when it got back.

[BetterRed]

Originally Posted by patrik

Interesting, could this be a linux-thing?

I guess it could be a linux thing, especially if Qt has a dog in the race.

The CV Window positions to the start of the PV paragraph in which you click - not to the exact place at which you click. So, if you click at the end of a long paragraph in PV, the CV window could reposition some distance prior. Monitor, window and font sizes have a bearing. I often have the CV text size quite a bit bigger than PV text - which can create an impression its not syncing correctly.

BR