Andreas Pakulat wrote:
> On 05.06.07 14:03:26, Matthew Woehlke wrote:
>> Andreas Pakulat wrote:
>>> Well, maybe this should be done on a
case-by-case basis, for example
>>> I don't see a reason to wait for showDiff(),
but for example
>>> showCommit() might make sense to wait for.
(think of doing something
>>> after the commit is done).
>> Yes, I can agree with that. Also is there a
detach() method of VcsJob
>> (i.e. something that says 'run, and I don't care
about the result, clean
>> yourself up')?
>
> No, and how should it delete itself? deleteLater in a
private slot
> connected to finish()? I don't like that. After all the
user explicitly
> requests a VcsJob from the version control interface so
he's responsible
> for properly deleting it.
I think the question here is what is the best way to address
both users
that may want to wait on the User to finish using a GUI, and
users that
want to 'run and forget'.
--
Matthew
...yzarc gniog ylwols era uoY
_______________________________________________
KDevelop-devel mailing list
KDevelop-devel kdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinf
o/kdevelop-devel
|
