Sigil 2.7.5 Release Candidate (RC) Now Available

[DiapDealer]

Originally Posted by DNSB

Thanks! I'm moving on to playing with PageEdit now.

Reminds me that PageEdit's Windows CI process will probably still be caching the older broken Qt6.10.2

[DNSB]

Originally Posted by DiapDealer

Reminds me that PageEdit's Windows CI process will probably still be caching the older broken Qt6.10.2

Like trying to stomp a cockroach?

[BetterRed]

Originally Posted by DNSB

Looks good here. The About box, Preferences, Metadata Editor, Edit Table of Contents, Saved Searches, etc. have only the exit button, Reports & Spellcheck minimize to the status bar. I'm going to have to re-install 2.7.0 to see if there are any changes I am missing.

Really - to the status bar, is that on Win 10 or 11? I distinctly recall KH saying he didn't want that.

Perhaps someone can test with these settings on Win 10.

BR

[DiapDealer]

The three dialogs in question minimize to just above the Windows task bar (on the left side of the screen) on Windows 10 and 11. That's with default taskbar settings. Just like they did when you tested the older Sigil 2.7.5 beta. https://www.mobileread.com/forums/sh...18&postcount=3

[DNSB]

Originally Posted by BetterRed

Really - to the status bar, is that on Win 10 or 11? I distinctly recall KH saying he didn't want that.

Perhaps someone can test with these settings on Win 10.

BR

The status bar just above the task bar at the bottom of the screen. The same behaviour on Windows 11 (physical and a preview VM) and a Windows 10 VM (22H2, build 19045). The attached image is from the Windows 11 VM (25H2 26220.7859) running my latest build of Sigil.

[KevinH]

And for the record I do not care where they go as long as the user has more screen room when they are minimized and can get them back when needed.

[BetterRed]

Originally Posted by DiapDealer

The three dialogs in question minimize to just above the Windows task bar (on the left side of the screen) on Windows 10 and 11. That's with default taskbar settings. Just like they did when you tested the older Sigil 2.7.5 beta. https://www.mobileread.com/forums/sh...18&postcount=3

I did not test Sigil 2.7.5 beta with the Windows 10 default taskbar settings. I tested it with the settings I posted above: Taskbar on the left, buttons combined with no labels.

With that configuration parking mini-titlebars bottom left is a bit like putting an ad in Vanity Fair, bottom left verso… cheap seats.

How many more rotten eggs are in this version of Qt I wonder.

BR

[BetterRed]

Originally Posted by KevinH

And for the record I do not care where they go as long as the user has more screen room when they are minimized and can get them back when needed.

Kevin - I can't recall why parking them in the status bar was rejected during beta tests… perhaps because they would get in the way of something else, or be hidden by something else.

I have RC2, I'll give it a spin.

BR

[KevinH]

It was never an issue for me in the Beta or now. Again where it shows up differs by OS and is not my concern. Freeing up space easily is what we were shooting for, for small screens.

[KevinH]

If people turn out to not like minimizing things, we can try our option B fir a future release.

[BetterRed]

So ran RC2 on Windows 10, I still get the mini-title bars at bottom left when I minimise a non-modal window, hard to see, hard to access (with the keyboard) etc.



So I restarted Windows in safe mode to eliminate my Windows addons, when I started Sigil i got this error:

Traceback (most recent call last):

  File "C:\Program Files/Sigil/python3lib\xmlprocessor.py", line 5, in <module>
    from sigil_bs4 import BeautifulSoup

  File "C:\Program Files/Sigil/plugin_launchers/python\sigil_bs4\__init__.py", line 34, in <module>
    from .builder import builder_registry, ParserRejectedMarkup

  File "C:\Program Files/Sigil/plugin_launchers/python\sigil_bs4\builder\__init__.py", line 7, in <module>
    from sigil_bs4.element import (
    ...<3 lines>...
        )

  File "C:\Program Files/Sigil/plugin_launchers/python\sigil_bs4\element.py", line 8, in <module>
    from pdb import set_trace

  File "pdb.py", line 87, in <module>

  File "asyncio\__init__.py", line 45, in <module>

  File "asyncio\windows_events.py", line 8, in <module>

OSError: [WinError 10050] A socket operation encountered a dead network

Suggestions for next release - a) disable plugin option in Manage plugins, b) make all plugins fault tolerant to dead network.

Scratch that, removed the plugins and got the same error. I'll try Safe mode with network - grhhh

Sigil runs OK in Windows 10 Safe mode providing it has a network, maybe it could be made fault tolerant to the dead network condition.

However when a non-modal window is minimised it lands outside the main window, just as it did when my add-ons were running. viz:



I suspect @DNSB was running Sigil full screen and the mini-titlebars only appeared to be in Sigil's status line, i.e. it was an illusion. Those windows have a locked on top flag set… I recall there being such a thing back when MDI was flavour of the month.

If non-modal windows could be parked in the status line that would be perfect. No need for mini-title bars, a button with a corresponding keyboard shortcut for each would suffice.

BR

[Turtle91]

Originally Posted by KevinH

Yes that is where they asked for it to go as far as I could tell.

Opening an xhtml can be done in multiple ways. Going to a single instance in an xhtml file when that class could be used in any number of xhtml files makes little sense. That list is not complete that field is there to illustrate it is being used.

Where it is used in xhtml files when it may be used lots of times in multiple places (not just the randomly chosen link in the Report table) is best done by Find and Replace.

So it works as designed as far as I can tell.

The current (pre- RC) takes you to the top of the xhtml page corresponding to the line which you double click on. It has been that way for as long as I can remember.

The request, Post #46 in the Suggestions for Sigil Improvements thread, and your reply in post #48 mentioned:

3) You can double click on a file in Classes Used but the cursor is postitioned at the start of the file. Would it be possible to position the cursor at the first occurance of the class shown? If this can't be done would it be possible to allow us to copy the class name and then search for it in Find and Replace?

and your reply:

3. You can already right click in a class in the editor and Sigil will take you directly to it in the css. I will look into allowing the Classes Used Report to do the same.

ctrl-clicking on the class name in an xhtml will take you to the css location (if it is linked and it can find it) on the stylesheet.

double-clicking on the Classes Used takes you to the top of the xhtml page referenced on the line you click on.

I use this functionality all the time when I am cleaning up classes with nonsense names. When I find a class that is a simple style (eg. italic, or bold) then using find/replace is usually the best answer. However, if there are more complex classes - especially when used relative to surrounding classes - then I like to see how the style is presented by going to the actual xhtml page. So the above request to go to the first occurrence of the class on the xhtml xhtml page makes more sense.

I do like the idea of being able to go directly to the css occurrence, so using ctrl-click on the Classes Used page would be consistent with that functionality when used in the coding view. Perhaps using right-click on the class name to highlight the name (or automatically place it in the Find field) would be helpful as well.