https://bugs.kde.org/show_bug.cgi?id=284148 --- Comment #9 from Andreas Pakulat 2011-11-28 22:00:48 --- Why does a plugin register a KIO job with the KDevelop run interface? I think a plugin should only register its own internal job-objects or job-objects obtained from the KDevPlatform API with the runcontroller. In particular it'll be surprising for the user that a KIO copy job is not showing up where its usually showing up. Maybe we should've created a KDevelop::JobController and a KDevelop::Job to make it clearer for plugin-authors they should only register those jobs and leave kio-jobs and others 'elsewhere'. That being said, this clearly marks a bug in kdelibs, KIO::Job shouldn't crash if its ui-delegate is changed to something non-KIO. It either needs to be able to cope with the situation, or disallow changing the delegate in the first place (making the API private or re-implementing it and doing nothing in it). -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ KDevelop-bugs mailing list KDevelop-bugs@kdevelop.org https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-bugs