Sigil 0.8.0 Released

[varlog]

Originally Posted by Hitch

+1.

Varlog:

Hey, as long as you're happy to answer all the questions from all the users that have issues due to it, great. I don't mean to sound snippy, but the truth is, a huge percentage of the posts on the Sigil forum are about "bugs" (hmph) that happen because John Doe thinks it's a word-processor and TREATS it as such.

it is too general statement for me. Cannot judge its relevance, point me to actual cases?

I don't understand why "preview" isn't good enough. I don't care about taking the option away from you, as long as the rest of us (who don't use it) don't have to reply to all the questions caused thereby. And, to be clear, that we aren't expected to support further enhancements in that (the word-processing/WYSIWYG) area, over productivity enhancements.

Hitch

I will have to look at preview again. Because of my personal pursuits it could be that I am somehow not in the picture perhaps.
Nevertheless I think preview is something above casual user (just looked at it). I think casual user uses BookView. I did. And do! Knowing what I do.

Getting casual users hooked is a feature Sigil should not lose. They will advance or not. Professionals, as you, won't have problems with advancing. The rest of us will too - according to needs and abilities. Be generous. It is open source.

[blackest]

Originally Posted by Hitch

+1.

Varlog:

Hey, as long as you're happy to answer all the questions from all the users that have issues due to it, great. I don't mean to sound snippy, but the truth is, a huge percentage of the posts on the Sigil forum are about "bugs" (hmph) that happen because John Doe thinks it's a word-processor and TREATS it as such. Sigil isn't now, and never WAS, intended to run like that. Even when Valloric first introduced it, it was never supposed to be a replacement for Word or OO or whatever-your-flavor-is. I suspect it never will be. What are we at now, in terms of lines of code? AT 7, it was what, a million lines? Do we really think that the guys will add the other 5 million lines of code that are needed to make it actually work LIKE a Word processor?

I don't understand why "preview" isn't good enough. I don't care about taking the option away from you, as long as the rest of us (who don't use it) don't have to reply to all the questions caused thereby. And, to be clear, that we aren't expected to support further enhancements in that (the word-processing/WYSIWYG) area, over productivity enhancements.

Hitch

problem i find with preview is getting it to the right size and it seems a bit crash prone when dragging it around.

Book mode is pretty awesome, you know you can select a load of stuff on a webpage and copy and paste it into bookview. It probably makes quite a good tool for producing webpages too, a lot less buggy than kompozer on linux if not quite so easy to use in someways.

I guess that i'd love to see sigil localise or cache links well images specifically. it'd be easier than manually downloading each image and then changing the links to ..\Images\picture1.jpg (guess thats just being lazy really).

[DaleDe]

I believe the WYSIWYG mode was for simple changes like fixing typos for users who can invoke Sigil on an existing ePub but are not power users. I guess it depends on the target audience or audiences. It worked well for fixing typos.

Dale

[theducks]

Originally Posted by blackest

problem i find with preview is getting it to the right size and it seems a bit crash prone when dragging it around.

Book mode is pretty awesome, you know you can select a load of stuff on a webpage and copy and paste it into bookview. It probably makes quite a good tool for producing webpages too, a lot less buggy than kompozer on linux if not quite so easy to use in someways.

I guess that i'd love to see sigil localise or cache links well images specifically. it'd be easier than manually downloading each image and then changing the links to ..\Images\picture1.jpg (guess thats just being lazy really).

What OS?
I use it all the time (undocked) on my 3rd (USB connected) Monitor.
I move it, Resize it. OK, I have not docked it in a coons age.

Crash! The only 100% guaranteed crash is Using the HTML TOC tool after doing other (including those saved just prior) edits on the book. This (still) happens on W7 and XP.

[theducks]

Attempt to dock on XP = Crash
Any way I tried: Double-click Header, Drag and Drop (it docks then crashes)

W7 I can dock/un-dock all I want..

QT5 on XP?

[KevinH]

Hi,

I never use the HTML TOC tool so I have never run into this bug. So will you please provide a specific sequence of steps to recreate this crash with with a testcase ebook you might have and be willing to post so that I can recreate it.

If I can reliably recreate it I should be able to fix it.

Thanks,

Kevin

Originally Posted by theducks

What OS?
I use it all the time (undocked) on my 3rd (USB connected) Monitor.
I move it, Resize it. OK, I have not docked it in a coons age.

Crash! The only 100% guaranteed crash is Using the HTML TOC tool after doing other (including those saved just prior) edits on the book. This (still) happens on W7 and XP.

[theducks]

Soon as I say something I tried to compile a sequence list.

It was like clockwork on XP and W7.
90% of the time a crash (i think it was replacing the previous one )

You would see the new one appear, followed quickly by the infamous Dr. Watson

[KevinH]

Hi theducks,

Just to verify ... we are talking about the button that completely recreates the HTML TOC, correct? Not the EditTOC menu item.

If so, I have spent about an hour trying to get the TOCHTMLWriter tool to crash. I simply can not. My build is with Qt 5.3.2 (an update over 5.3.1) so perhaps this was a bug in Qt5 that has now been fixed. I can only test on Mac OS X as well so perhaps this is a Windows specific bug.

Sorry, but without a way to recreate it (even once) I can not find the bug to fix it.

If run run into it again, please let me know.

KevinH

[Doitsu]

@KevinH

Can you test the following on your OSX machine:

1. Open Sigil without a book.
2. Press F10 or select Preview from the View menu.
3. Drag the Preview window to the area immediately below the lower Sigil tool bar and drop it there.
4. Select the Preview window with the mouse and try to move it back.

(These steps will trigger a crash on Linux machines, which I've already reported to DiapDealer.)

[DiapDealer]

Originally Posted by Doitsu

@KevinH

Can you test the following on your OSX machine:

1. Open Sigil without a book.
2. Press F10 or select Preview from the View menu.
3. Drag the Preview window to the area immediately below the lower Sigil tool bar and drop it there.
4. Select the Preview window with the mouse and try to move it back.

(These steps will trigger a crash on Linux machines, which I've already reported to DiapDealer.)

I can confirm this happens on the 32-bit Windows version (in addition to Linux), as well. Right at Step 3, actually, on my Vista 32-bit.

I've only been able to narrow the segfault down to QtCore (QObject::Disconnect) so far on Linux.

EDIT: Also happening for me on Win7 using the 64-bit 0.8.0 vers. of Sigil.

[theducks]

Originally Posted by KevinH

Hi theducks,

Just to verify ... we are talking about the button that completely recreates the HTML TOC, correct? Not the EditTOC menu item.

If so, I have spent about an hour trying to get the TOCHTMLWriter tool to crash. I simply can not. My build is with Qt 5.3.2 (an update over 5.3.1) so perhaps this was a bug in Qt5 that has now been fixed. I can only test on Mac OS X as well so perhaps this is a Windows specific bug.

Sorry, but without a way to recreate it (even once) I can not find the bug to fix it.

If run run into it again, please let me know.

KevinH

Tools: Table of Contents: Create HTML Table of Contents

1) this builds the TOC from the NCX

2) It almost never fails on a fresh (book) open. (After A crash, I build the HTML TOC just fine)
3) This issue has been there for quite some time (a PITA bug ).
Some odd race between the NCX, OPF and the HTML?

[KevinH]

Hi Doitsu,

On Mac OS X with Qt 5.3.2 I can not recreate this bug either.
I can move it just below the second tool bar and the main window nicely slides down to make space to dock it. I can then move it away and it nicely detaches to it own window. I can then move it to one side or the other side of the main window and it will nicely attach there as well. I can also move it away at will.

No crashes what so ever.

Sorry, but if DiapDelaer can recreate it then we should be able to get it fixed. Especially if it can be recreated on two platforms.

Sorry,

KevinH

Originally Posted by Doitsu

@KevinH

Can you test the following on your OSX machine:

1. Open Sigil without a book.
2. Press F10 or select Preview from the View menu.
3. Drag the Preview window to the area immediately below the lower Sigil tool bar and drop it there.
4. Select the Preview window with the mouse and try to move it back.

(These steps will trigger a crash on Linux machines, which I've already reported to DiapDealer.)

[KevinH]

Hi theducks,

Yes I was testing something else toc related (the creation of a new toc.ncx).

So I loaded a couple of books (Macs can have multiple windows open in the same app) and tried deleting the toc.xhtml, and using the Create HTML TOC menu item repeatedly in all of them and then adding new files to them and copying new items form one to the other but no crashes so far.

If it is a race of some sort, it can be very hard to trigger in one build but may be much easier to trigger in another build.

I will periodically keep trying to see if I can ever generate a crash.

Take care,

KevinH

Originally Posted by theducks

Tools: Table of Contents: Create HTML Table of Contents

1) this builds the TOC from the NCX

2) It almost never fails on a fresh (book) open. (After A crash, I build the HTML TOC just fine)
3) This issue has been there for quite some time (a PITA bug ).
Some odd race between the NCX, OPF and the HTML?

[KevinH]

Hi DiapDealer,

If you can make a Debug (instead of Release) build and get a good long backtrace of the crash in gdb or by some other way, I would love to see it.

Thanks,

KevinH

Originally Posted by DiapDealer

I can confirm this happens on the 32-bit Windows version (in addition to Linux), as well. Right at Step 3, actually, on my Vista 32-bit.

I've only been able to narrow the segfault down to QtCore (QObject::Disconnect) so far on Linux.

EDIT: Also happening for me on Win7 using the 64-bit 0.8.0 vers. of Sigil.

[DiapDealer]

Originally Posted by KevinH

Hi DiapDealer,

If you can make a Debug (instead of Release) build and get a good long backtrace of the crash in gdb or by some other way, I would love to see it.

Thanks,

KevinH

Hey Kevin,

Even with a debug build on Linux, I'm just not getting much insight into the Qt libraries themselves. The binary Qt 5 downloads for Linux don't have separate Release/Debug versions of the libraries like the Windows downloads do ... and I can't seem to figure out how to load (or turn on) the extra debugging symbols for Qt5 itself. I may have to resort to using the Windows debugging tools to get a helpful backtrace. I don't look forward to remembering how to do that.