[Differential] [Commented On] D2792: fix KDevelop::JobStatus for "short-lived" jobs

[antonanikin (Anton Anikin)]

antonanikin added a comment.


  > Again, this is not a problem but rather by design.
  
  Ok. But how to indicate "finished" status for jobs, which not show output during work? We can add the optional parameter for such "force" status showing , but this changes the API.
  
  > This sounds interesting. Can you clarify when this happens? Can you give us a way to reproduce this behavior? Looking at the existing code, it is not clear to me where this arises from. Also, again, I don't see how adding a timer would help in that situation.
  
  https://paste.kde.org/pipaf2s9l
  
  run:
  
    TestJob* testJob = new TestJob(1000, 5000);
    core()->uiController()->registerStatus(new KDevelop::JobStatus(testJob, "testJob"));
    testJob->start();
  
  If the value of first parameter is less than 1000 - we don't see any status (tested with master branch). I think it's not correct behavior :)

REPOSITORY
  rKDEVPLATFORM KDevPlatform

REVISION DETAIL
  https://phabricator.kde.org/D2792

EMAIL PREFERENCES
  https://phabricator.kde.org/settings/panel/emailpreferences/

To: antonanikin, kfunk, mwolff
Cc: mwolff, kdevelop-devel, #kdevelop
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20160930/c8f23191/attachment-0001.html>