[prev in list] [next in list] [prev in thread] [next in thread] 

List:       pykde
Subject:    Re: Widgets are not updated - is this a bug?
From:       Raymond Osborn <rayosborn () mac ! com>
Date:       2020-09-17 18:17:32
Message-ID: D00E6D9B-0768-4E2C-B2CF-CC92075C7A63 () mac ! com
[Download RAW message or body]

I have been mystified about the history of these bugs. I read several reports over the past two years saying that problems had been solved, with promises of a fix in the next release, but the issues I encountered, which are identical to the ones reported here, have persisted from v5.11 to 5.15. My day job doesn't really allow me to spend a lot of time pursuing these issues, so once I had fixed it for my own code by sub-classing the widgets and adding explicit calls to repaint(), I haven't worried about it. I was just responding to the request in this thread for information about previous Mac OS versions.

Ray

> On Sep 17, 2020, at 12:29 PM, Jeremy Katz <jkatz@volexity.com> wrote:
> 
> 
> 
> On 17/Sep/20 05:35, Raymond Osborn wrote:
>> I only use whatever is built by Conda or pip. I'm not aware what they
>> build against, but I had naively assumed there was some correspondence
>> between PyQt5 and Qt5 versions. There is some version information
>> here: https://bugreports.qt.io/browse/QTBUG-68740 and https://bugreports.qt.io/browse/QTBUG-68521.
>> 
>> Ray
>> 
> 
> Both of those defect reports are marked as closed. QTBUG-68740 has a fix
> version of Qt 5.11.2. The change appears to be
> https://codereview.qt-project.org/c/qt/qtbase/+/237788
> 
> https://bugreports.qt.io/browse/PYSIDE-695 and
> https://bugreports.qt.io/browse/PYSIDE-871 sound like the same issue,
> and are currently open. 695 mentions the style workaround. 871 has the
> same C++ versus Python disparity.

[prev in list] [next in list] [prev in thread] [next in thread]