View Single Post
Old 09-28-2014, 10:30 PM   #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 BetterRed View Post
You may recall I raised the apparent anomaly that Qt 5.3.1 did not create a problem with Sigil in the calibre/XP discussions, and I postulated that perhaps the problem was not in Qt itself but in the python wrappers.
It has nothing to do with the python wrappers. they're not even loaded unless you set a python path and run a plugin. It is due to Qt and the updated build chain.

Quote:
Originally Posted by BetterRed View Post
And for the record Kovid didn't stop supporting XP as a policy decision when he released 2.0. He made that decision after the release because of the excessive number of user reported problems on XP, and not without some reluctance/regret I suspect.
This is the reason I'm not putting effort into XP and made it a policy decision.
user_none is offline   Reply With Quote