https://bugs.kde.org/show_bug.cgi?id=360846
Chris Burel <chrisbu...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |FIXED
CC| |chrisbu...@gmail.com
--- Comment #2 from Chris Burel <chrisbu...@gmail.com> ---
I can't replicate the failure with the helpcontextsensitivehelp test, but I can
replicate the mainwindowsmdi test failure. This is fixed in c989a56d.
The problem was in PerlQt's method resolution. When there are method
overloads, it is supposed to determine the best method to call based on the
inheritance distance between the types of the arguments supplied, and the
method overloads. Specifically, consider the following two overloads:
QSignalMapper::setMapping(QObject* sender, QWidget* widget)
QSignalMapper::setMapping(QObject* sender, QObject* object)
Calling $mapper->setMapping($myObject, $myWidget) should resolve to the first
one, not the second.
There were two problems. First, the function that was designed to return the
inheritance distance was only returning 1 or -1, indicating a yes or no
respectively. This is fixed in 3a22e526.
The second problem was that even after the inheritance depth was returned
correctly, the precedence order of the methods was being lost. This is fixed
in 0b2b3da3.
http://commits.kde.org/perlqt/c989a56da7d887feabed9d2875550173c2ceabcb
--
You are receiving this mail because:
You are watching all bug changes.
