4.0 rc1 behavior

[alansplace]

with some files where i need to add a <h#> tag to and then insert a chapter break (i use ctl <enter>) the new html split created by the break goes above the cover. and this the screws up the order of the toc. to fix things i've been starting over with 3.6 and 3.6 works like it usually does.

[user_none]

What?

You're talking about adding an h tag then splitting. Then you talk about the cover (where does this come in at all). Finally, you reference a version that doesn't exist (I can understand getting the numbers mixed up or being off a little bit but there 0.3.4 is a long way from 3.6).

Can you rewrite the issue you're having and provide more detail of exactly what you're doing and what's happening?

[theducks]

Originally Posted by user_none

What?

You're talking about adding an h tag then splitting. Then you talk about the cover (where does this come in at all). Finally, you reference a version that doesn't exist (I can understand getting the numbers mixed up or being off a little bit but there 0.3.4 is a long way from 3.6).

Can you rewrite the issue you're having and provide more detail of exactly what you're doing and what's happening?

Split on Sigil Markers has always had split-off files placement issues (reported: not found) for me (any Sigil version on XP).

I had finally managed to screen captured the events and put together a bug report package, but never filed it.
Normal Sigil Splits always worked as expected.

[Pablo]

Originally Posted by theducks

Split on Sigil Markers has always had split-off files placement issues (reported: not found) for me (any Sigil version on XP).

I had finally managed to screen captured the events and put together a bug report package, but never filed it.
Normal Sigil Splits always worked as expected.

Not in my case! I always use "Split on Sigil Chapter Markers", and never had placement issues until 0.4, in fact, that's the reason why I went back to 0.3.4.

[alansplace]

Originally Posted by user_none

What?

You're talking about adding an h tag then splitting. Then you talk about the cover (where does this come in at all). Finally, you reference a version that doesn't exist (I can understand getting the numbers mixed up or being off a little bit but there 0.3.4 is a long way from 3.6).

Can you rewrite the issue you're having and provide more detail of exactly what you're doing and what's happening?

sorry it was past my bedtime when i hurried that together. yes, 3.4. ok....

in the left panel, normally when doing a split the new split appears right below the original one. but in this instance it appears at the very top of the list (above the cover split).

hope that makes more sense.

[st_albert]

Originally Posted by Pablo

Not in my case! I always use "Split on Sigil Chapter Markers", and never had placement issues until 0.4, in fact, that's the reason why I went back to 0.3.4.

Same here. We are using 0.3.4 in production (on Debian). The inability to perform "split on Sigil chapter markers" was a big-time dealbreaker for us. Ver 0.3.4 works flawlessly.

[theducks]

Originally Posted by Pablo

Not in my case! I always use "Split on Sigil Chapter Markers", and never had placement issues until 0.4, in fact, that's the reason why I went back to 0.3.4.

It consistently places split-off files at the END of the book if I use Split on Markers.
I used S&R to place markers before chapter headings (confirmed) them I pressed F6. (NB the long name is the parent. I expected/need the splits to immediately follow the parent)

[st_albert]

Originally Posted by theducks

It consistently places split-off files at the END of the book if I use Split on Markers.
I used S&R to place markers before chapter headings (confirmed) them I pressed F6. (NB the long name is the parent. I expected/need the splits to immediately follow the parent)

OK, that's why I never have problems. I always start with a single file containing all the split markers, then split-on-markers all at once. So if it starts at the beginning, there's no place for the split off part to go BUT the end.

If I need to split something else out after that, I place the cursor at the split point, and use the "split chapter" button. That works for me.

[theducks]

Originally Posted by st_albert

OK, that's why I never have problems. I always start with a single file containing all the split markers, then split-on-markers all at once. So if it starts at the beginning, there's no place for the split off part to go BUT the end.

If I need to split something else out after that, I place the cursor at the split point, and use the "split chapter" button. That works for me.

My work around has to only mark(up) 1 segment at a time and split, then drag the next unmarked to the end and repeat the mark-split sequence.
Until I worked this out, I had a total mess

[Pablo]

Originally Posted by st_albert

OK, that's why I never have problems. I always start with a single file containing all the split markers, then split-on-markers all at once. So if it starts at the beginning, there's no place for the split off part to go BUT the end.

If I need to split something else out after that, I place the cursor at the split point, and use the "split chapter" button. That works for me.

That's exactly my case, maybe that's why I haven't noticed the problem...

[charleski]

I've fixed several distinct issues with chapter splitting. There was one final problem with element ids and ToC generation that I only discovered and fixed yesterday, but that will go into the next release, which will be soon. Right now you have to make sure that all heading tags that aren't at the start of a flow have an id for the ToC to work properly, but that requirement will soon go away and Sigil will generate them automatically.

Split on SGF Chapter Markers should work exactly as expected in 0.4.0RC2, with no need to resort to workarounds or shuffle the files. The new chapters will now be placed in order immediately after the original chapter from which they were split and will be named [original file name]-0002, -0003, etc. This will work no matter where the original chapter is in the reading order.

Please test out 0.4.0RC2 and check that chapter splitting works properly in all cases. It was the main blocking issue that I wanted to resolve for the final release.

[st_albert]

For what it's worth, I gave the Apple version of 0.4.0-RC2 a quick run-through and all the chapter splitting things seemed to be resolved, including IIRC the split button to divide one chapter into two. I have not tried the Win version.

Also FWIW, yesterday morning I cloned the sigil repository and built Sigil on Ubuntu and on Debian. On both, most everything seemed to work except that the program hangs when the "generate toc" button is pressed. I realize that the cloned repository probably contained several commits beyond RC2, so I don't know how meaningful my results are. To say nothing of the issue of whether I built it correctly or not (though a build of 0.3.4 worked fine).

I only mention it since you said you've been messing with the TOC-building code, so possibly something got broken.

[charleski]

Originally Posted by st_albert

most everything seemed to work except that the program hangs when the "generate toc" button is pressed

Yeah, oops, the fix for that will go through soon.

[st_albert]

Originally Posted by charleski

Yeah, oops, the fix for that will go through soon.

And it has, and it's fixed! :

I will note in passing that on the KDE desktop, it still suffers from (evidently) some conflict with KDE's QT libraries. But the workaround discussed here works. I just added the code to unset the QT_PLUGIN_PATH variable in the sigil.sh script file, and it's good to go.

I tried both methods of file splitting as well as dragging files in the book browser to re-order them, and then re-build the TOC. All works as expected.

[alansplace]

i just made some changes (search for something, replace with nothing) in code view on all html files. then when i clicked on the windows red x in the upper right corner sigil closed without its usual question as to whether it should save my changes. had to do it all over again and choose 'save' in the 'file' drop-down.