Review Request 127017: Fix click event for constant buttons

[Luigi Toscano]

> On March 8, 2016, 8:50 p.m., Rolf Eike Beer wrote:
> > According to what I know one needs to use the class that introduced the signal, so this change seems correct.

Thanks! I guess I need to look better in the Qt documentation.


- Luigi


-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/127017/#review93311
-----------------------------------------------------------


On March 7, 2016, 1:18 a.m., Luigi Toscano wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://git.reviewboard.kde.org/r/127017/
> -----------------------------------------------------------
> 
> (Updated March 7, 2016, 1:18 a.m.)
> 
> 
> Review request for KDE Utils, Christoph Feck, Rolf Eike Beer, Laurent Montel, and Evan Teran.
> 
> 
> Bugs: 353644
>     http://bugs.kde.org/show_bug.cgi?id=353644
> 
> 
> Repository: kcalc
> 
> 
> Description
> -------
> 
> It looks like the new style of "connect" tries to use the clicked signal as defined inside the function, which does not trigger slotClicked(). This change explicitly use the clicked signal from the (grand)parent class and the expected chain of signal/slots triggering is restored.
> (that said, I'm not too expert on debugging the internals of the signal/slot system, so I may have guessed incorrectly).
> 
> 
> Diffs
> -----
> 
>   kcalc_const_button.cpp 443abb6 
> 
> Diff: https://git.reviewboard.kde.org/r/127017/diff/
> 
> 
> Testing
> -------
> 
> Constant buttons can be clicked again
> 
> 
> Thanks,
> 
> Luigi Toscano
> 
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-utils-devel/attachments/20160308/279cd37d/attachment.html>