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
>
>
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
I am using currentWidget to get the current tab, but it doesnt work 100%
correctly for me
ie : i have 3 tabs, Root, Arm, Leg
if I select leg, it will print leg. if I select arm, it will print leg,
and if I select arm again, it will print arm this time.
very first selection will print