View Single Post
Old 04-21-2016, 09:57 AM   #10
DiapDealer
Grand Sorcerer
DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.
 
DiapDealer's Avatar
 
Posts: 28,661
Karma: 205039118
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
Quote:
Originally Posted by HarryT View Post
Would one not, in that case, also expect the same issue to arise in other applications which use Qt, such as Calibre? I don't recall ever having seen this issue reported in Calibre.
It's pretty rare in the first place (both because it IS device specific and because not a lot of people right-click inside of a file-open dialog) The fact that you've not heard of the issue happening with calibre does not mean that it never does (or ever did). Kovid is also more willing to go a lot of extra miles to work around Qt limitations/issues than I am. It's quite admirable on his part, but unless it's a wide-spread issue that's easily reproduceable (and affects a significant portion of the userbase in a dramatic way), I tend to want to leave Qt bugs for Qt to fix (or not).

If someone were to come up with definitive steps to reproduce this particular Qt/Windows/C++ chupacabra consistently (or Kovid points us to where he's encountered and beaten this bug), then a workaround will certainly be quickly sought to remedy it, if at all possible.

Last edited by DiapDealer; 04-21-2016 at 10:00 AM.
DiapDealer is offline   Reply With Quote