[libcalamares] Explain updating-status-text mechanism
This commit is contained in:
parent
fb83ad326b
commit
fe68b45fc5
@ -188,6 +188,13 @@ private:
|
|||||||
// starts the job, or if the job itself reports 0.0) be more
|
// starts the job, or if the job itself reports 0.0) be more
|
||||||
// accepting in what gets reported: jobs with no status fall
|
// accepting in what gets reported: jobs with no status fall
|
||||||
// back to description and name, whichever is non-empty.
|
// back to description and name, whichever is non-empty.
|
||||||
|
//
|
||||||
|
// Later calls (e.g. when percentage > 0) use the status unchanged.
|
||||||
|
// It may be empty, but the ExecutionViewStep knows about empty
|
||||||
|
// status messages and does not update the text in that case.
|
||||||
|
//
|
||||||
|
// This means that a Job can implement just prettyName() and get
|
||||||
|
// a reasonable "status" message which will update only once.
|
||||||
if ( percentage == 0.0 && message.isEmpty() )
|
if ( percentage == 0.0 && message.isEmpty() )
|
||||||
{
|
{
|
||||||
message = jobitem.job->prettyDescription();
|
message = jobitem.job->prettyDescription();
|
||||||
|
Loading…
Reference in New Issue
Block a user