Review Request: Avoid Resetting UI Delegates

Aleix Pol Gonzalez aleixpol at gmail.com
Thu Dec 1 02:27:43 UTC 2011


-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/103285/#review8632
-----------------------------------------------------------


I'd say the best thing to do would be not to register this job but let the caller to manage its destruction.

- Aleix Pol Gonzalez


On Nov. 28, 2011, 8:17 p.m., David Narváez wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> http://git.reviewboard.kde.org/r/103285/
> -----------------------------------------------------------
> 
> (Updated Nov. 28, 2011, 8:17 p.m.)
> 
> 
> Review request for KDevelop.
> 
> 
> Description
> -------
> 
> Avoiding so decreases chances that bugs similar to bug 284148 happen again (it closes that bug, in particular). Notice that it would now be the responsibility of the KDevelop::RunController::registerJob(KJob *) caller to set the UI Delegate it wants to use before the call in case the job requires a UI Delegate different from KDialogJobUiDelegate (see the discussion in the bug report for a reason for that). 
> 
> 
> This addresses bug 284148.
>     http://bugs.kde.org/show_bug.cgi?id=284148
> 
> 
> Diffs
> -----
> 
>   shell/runcontroller.cpp 421a232 
> 
> Diff: http://git.reviewboard.kde.org/r/103285/diff/diff
> 
> 
> Testing
> -------
> 
> I've been using this patch for about three weeks with no problems related to the UI Delegate.
> 
> 
> Thanks,
> 
> David Narváez
> 
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20111201/72e08dc5/attachment.html>


More information about the KDevelop-devel mailing list