View Single Post
Old 01-05-2012, 08:37 AM   #13
user_none
Sigil & calibre developer
user_none ought to be getting tired of karma fortunes by now.user_none ought to be getting tired of karma fortunes by now.user_none ought to be getting tired of karma fortunes by now.user_none ought to be getting tired of karma fortunes by now.user_none ought to be getting tired of karma fortunes by now.user_none ought to be getting tired of karma fortunes by now.user_none ought to be getting tired of karma fortunes by now.user_none ought to be getting tired of karma fortunes by now.user_none ought to be getting tired of karma fortunes by now.user_none ought to be getting tired of karma fortunes by now.user_none ought to be getting tired of karma fortunes by now.
 
user_none's Avatar
 
Posts: 2,487
Karma: 1063785
Join Date: Jan 2009
Location: Florida, USA
Device: Nook STR
Quote:
Originally Posted by dynabook
Does it require Lion or did you only test it with Lion?
Yes, the standalone Qt libraries for OS X will only work on Lion.

Quote:
Originally Posted by theducks
No longer remembers last Main window shape and position.
I'll look into this. It sounds like it's an issue with switching to Qt 4.8.

Quote:
Originally Posted by Jabby
What about leaving the display up until the next operation?
Let me think about leaving it up vs making the delay longer.

Quote:
Originally Posted by WS64
The bug with the umlauts is not fixed, if you rename a file and add german umlauts you can't rename the file again.
I knew I was forgetting something.

Quote:
Originally Posted by meme
I noticed that if I highlighted some characters in the same line it was white/white but if I drag to the next line or so that the text would highlight ok. At first I though after some googling that it was using palette instead of setStyleSheet, but it looks like its more to do with CodeViewEditor::HighlightCurrentLine(). It looks like the code to highlight the whole line line is conflicting with the highlighting of the selected text. If I comment out the HighlightCurrentLine code, it highlights ok. And if I put setStyleSheet("QPlainTextEdit { selection-background-color: darkBlue; selection-color: white }"); as the last line of HighlightCurrentLine then that works ok too (forcing the selection highlight after the line highlight). Neither of these seems a perfect fix, but something for you to consider.
I'll take a look.

Quote:
Originally Posted by Rand Brittain
Is this spell-check supposed to correct things in the document on its own? Because I've just opened an EPUB in Book View, spotted a lack of a space between a period and the next sentence, and switched to Code View only to find it not there anymore.
The spell checker does not do auto correction. Most likely this is due to how BV is rendering the document.

Quote:
Originally Posted by Toxaris
Case 1. Search for <a, first by accident RegEx, current file. Then set to Normal, all HTML files. Got a warning that it was in BV. Switched to CV and pressed find next. Crash. Not repeatable.

Case 2. Second crash. Opened the same book, it opens the cover in BV. I change to CV and doubleclick a xhtml file. Crash. Repeatable. From what I see, it appears that Sigil first wants to open it in split view and then changes to CV. It also crashes for other xhtml files.
I'll give this a try and see if I can recreate it. You use Linux right? Would it be possible for you to run Sigil in gdb and send me a back trace when you get it to crash?


FYI, The Linux builds are not going well and will be delayed a bit longer.
user_none is offline