[PySide] re-implementing setDown() for custom button
Frank Rueter | OHUfx
frank at ohufx.com
Thu May 3 08:23:52 CEST 2012
I'm kinda stuck with this one unfortunately.
On 2/05/12 6:35 PM, Frank Rueter | OHUfx wrote:
> sorry for the monolog, but I just realised I will also have to make my
> custom button play along when it's parent's self.sender() function is
> called as well.
> The QSignalSender doesn't quite seem to be the right thing to use as it
> is implemented in the parent's constructor, however I would like to
> implement this in the button's class if possible to make it self contained.
> How would I go about that?
> On 2/05/12 5:44 PM, Frank Rueter | OHUfx wrote:
>> to follow up my previous mail, I also just noticed that I have to
>> re-implement the QAbstractButton's setDown() function to make sure my
>> custom button doesn't stay down after a drag&drop action.
>> With a QPushButton I simply called self.setDown( False ) from inside the
>> mouseMoveEvent, so now I'm trying to understand how to recreate this
>> behaviour when using a custom paintEvent().
>> Any tips would be greatly appreciated.
>> PySide mailing list
>> PySide at qt-project.org
> PySide mailing list
> PySide at qt-project.org
More information about the PySide