[Kde-bindings] [Bug 211070] New: Missing support in PyKDE4 for KIO.Job's result( KJob *) signal using the new stype API

Luca Beltrame einar at heavensinferno.net
Mon Oct 19 11:28:43 UTC 2009


https://bugs.kde.org/show_bug.cgi?id=211070

           Summary: Missing support in PyKDE4 for KIO.Job's result( KJob
                    *) signal using the new stype API
           Product: bindings
           Version: unspecified
          Platform: SuSE RPMs
        OS/Version: unspecified
            Status: NEW
          Severity: normal
          Priority: NOR
         Component: general
        AssignedTo: kde-bindings at kde.org
        ReportedBy: einar at heavensinferno.net


Version:            (using KDE 4.3.2)
Installed from:    SuSE RPMs

In parallel with the changes in recent versions of PyQt, PyKDE4 has adopted the
new style API for signal/slot connections (i.e. OBJECT.SIGNAL.connect(SLOT) ). 
It works perfectly in most of the bindings, but in KIO.Job and derived
subclasses there is no way to access the "result" signal without using the old
API (SIGNAL("C++ signature")).

Given an example job:

get_job = KIO.get(KUrl("http://www.example.com/index.html"))

This is possible:

QtCore.QObject.connect(get_job, QtCore.SIGNAL("result( KJob *)"), some_slot)

while this raises an exception, as "result" is not present in "get_job":

get_job.result.connect(some_slot)

As new-stype API is also used in other parts PyKDE4, this should - if
technically possible - be addressed.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the Kde-bindings mailing list