0.6 Beta take 2 (0.5.905)

[mrmikel]

No, not the clipboard, just the displayed highlighting.

[theducks]

Originally Posted by mrmikel

No, not the clipboard, just the displayed highlighting.

[mrmikel]

Some of these things are pretty subtle, like the pasting problem which has been with Sigil for years. But it takes a specific set of actions like spacing after a paste to set it off, which other users may not do at all.

Nothing you can do in book view changes it, but switching to code view and back to book view clears it.

[kiwidude]

@mrmikel - the pasting issue is a Qt Webkit bug, which is why it has been around for years. Nothing Sigil can do about it. Note you can also clear it by making a new selection over the top of the one that got put there.

[roger64]

Linux Debian amd64

The building process was rather long but successfull following the instructions. After that Sigil opens instantly and looks pretty fast. Not tried yet.

[Oldpilot]

It stalls and crashes on me, even when I try to open a html file that I successfully converted to an epub three days ago using Sigil.

I will try rebooting my computer.

Sigh.

[meme]

I've uploaded a new HTML version of the Sigil User's Guide. The Help->User Guide menu entry should take you there.

Lots of work needed for the new features sections, but the basics are there. Tutorials and FAQ need updating once the UI is frozen.

[theducks]

Severe slowdown after doing a Merge on XP SP3 .
Quit and restart Sigil and speed is back

[meme]

Originally Posted by theducks

Severe slowdown after doing a Merge on XP SP3 .
Quit and restart Sigil and speed is back

Oh, good. Working as expected :-)

[kiwidude]

@theducks - I have just fixed (for the next release) some performance issues for Close Tabs, Close Other Tabs and also as it happens Open Tab (if you open lots of tabs progressively). All these operations get a fraction slower the more tabs you open in the current beta. The cause is that any time you open or close a tab every single other tab that is open would be refreshing its spelling/syntax highlighting, hence the progressive slowdown.

I believe your merge issue would also be likely affected by this. Particularly if you had the merged tab still open, and were just trying to open/close other tabs - as it would be recalculating highlighting on the (large) merged document every time. If that fits with what you saw then great. If however you had closed the merged tab, had only a single document tab open and still experienced slow operation, then that is something else I am not seeing. What exactly was slow - opening/closing tabs or something else?

Further performance tuning was always intended at some point but getting it all working and stable has been the priority. It's definitely trending in the right direction now though.

[theducks]

Originally Posted by kiwidude

@theducks - I have just fixed (for the next release) some performance issues for Close Tabs, Close Other Tabs and also as it happens Open Tab (if you open lots of tabs progressively). All these operations get a fraction slower the more tabs you open in the current beta. The cause is that any time you open or close a tab every single other tab that is open would be refreshing its spelling/syntax highlighting, hence the progressive slowdown.

I believe your merge issue would also be likely affected by this. Particularly if you had the merged tab still open, and were just trying to open/close other tabs - as it would be recalculating highlighting on the (large) merged document every time. If that fits with what you saw then great. If however you had closed the merged tab, had only a single document tab open and still experienced slow operation, then that is something else I am not seeing. What exactly was slow - opening/closing tabs or something else?

Further performance tuning was always intended at some point but getting it all working and stable has been the priority. It's definitely trending in the right direction now though.

Everything gets (and stays slow) slow, once I have done a Merge. Searches, saves, BV<=>CV. "Not responding" is frequently seen.
All cured by a restart of Sigil.


Yes, multiple tabs were open.
Yes, the Merge source was definitely open, and I believe the destination was either open or auto-opens upon merge.

[user_none]

@Oldpilot, A lot more information would be helpful. Such as OS and OS version? Did you do a fresh install or install over a previous version of Sigil? Does an uninstall followed by an install make a difference?

@theducks, If you do multiple merges does it get progressively slower? Can you open task manager and see if memory usage is going up and never going down?

[kiwidude]

@theducks - the actual "trigger" for slowness in that beta version is any of these sorts of actions with multiple tabs open:

• Switching BV/CV/PV
• Switching tabs
• Find operations (which result in the above)
• Closing/Opening tabs

Does the slowdown still continue once you are back down to a single tab open (preferably not a huge merged one of course)?

Does the slowdown happen if you don't open any of those merged tabs at all - i.e. Open Sigil, immediately merge files in the book browser, and just work with a small number of other tabs?

You don't have a linux box to try the latest source on by any chance do you?

[DiapDealer]

I built 0.5.905 on Ubuntu 11.10 64-bit. The build process went flawlessly. When done, I can run the newly created sigil binary from the "bin" directory of the build environment just fine. However... after "make install", I get the dreaded "/usr/local/bin/sigil: symbol lookup error: /usr/local/bin/sigil: undefined symbol: _ZN6QMutex12lockInternalEv" whenever I try to run it.

[meme]

Are you running sigil or sigil.sh ? Try the other.

I'm compiling/running fine on 12.04.