|
@BR: While I am far from understanding all the different ways Qt 5 crashes in XP. Here is one that I did look into in detail.
The calibre editor has much more sophisticated syntax highlighting than Sigil. You get to see matching tags, text inside headings/bold tags is shown in bold, you get live css, where the displayed css tracks the position of your cursor in the editor and so on. All these features mean that syntax highlighting is slower than in Sigil, as it has to fully recognize matching opening and closing tags. As a result, the calibre editor is designed to run it asynchronously in the background. This is causing crashes inside Qt only on XP and only with Qt 5. Making it synchronous again, stops the crashes, but greatly degrades performance. And this is just one crash that I happened to look into in detail, because I could easily replicate it in my XP VM.
There are several more that have been reported on XP machines. As such, Qt 5 + XP simply dont mix. Given that the crashes are a mix of XP and the actual computer hardware involved, debugging them is pretty hard as well. Running calibre 2.x on XP is *not a good idea*. You will get random crashes, that in the worst case will cause loss of data/file corruption.
So once more, I am not going to support running calibre 2.x on XP. It simply is not going to happen. I appreciate that people using XP dont like this decision. But calibre 1.48 remains available and works just fine on XP. After all if you are using XP you are fine with not getting the OS updated anymore, so so it is hardly fair that you complain when you dont get application updates. There is a price to be paid for using a 13 year old OS that is not supported by its manufacturer anymore.
Stay with calibre 1.48 for as long as you want to stay on XP. Pretend that I have decided to take a year long vacation from calibre and there are no more updates, for anybody. calibre 1.48 is a perfectly fine, stable and functional piece of software.
|