Interesting. One would think that if the signal is firing, that the state
of the QTabWidget should now be accurate. I guess use that approach
as-needed when you see this kind of lag in the state :-)
On Wed, Aug 9, 2017 at 3:55 PM Todd Widup wrote:
> ah that works :D
>
> thanks Justin
>
> On T
ah that works :D
thanks Justin
On Tue, Aug 8, 2017 at 8:45 PM, Justin Israel
wrote:
> Are you connecting to QTabWidget.currentChanged() signal to respond and
> print the currentWidget() value? If so, can you see if it makes a
> difference if you do your connection like this:
>
> tabWidget.curr
Are you connecting to QTabWidget.currentChanged() signal to respond and
print the currentWidget() value? If so, can you see if it makes a
difference if you do your connection like this:
tabWidget.currentChanged.connect(self.someSlot, QtCore.Qt.QueuedConnection)
Similar threads have reported a lag
