| Summary: | [HOB] Stop vs. Force Stop needs more visual guidance | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] Hob | Reporter: | Jiajun Xu <jiajun.xu> |
| Component: | hob | Assignee: | Joshua Lock - Disabled <josh> |
| Status: | VERIFIED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium | CC: | jessica.zhang, lianhao.lu, liping.ke, poky.bs.watcher, poky.watcher |
| Version: | unspecified | ||
| Target Milestone: | 1.1 M3 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | --- | |
|
Description
Jiajun Xu
2011-07-07 01:39:42 UTC
I am familiar with this issue however I'm not certain what to do about it. The force stop option could be removed or the dialog message could be enhanced to be more informative as to what the two options will do. Any thoughts? For more information - force stop is the equivalent of hitting Ctrl-C at the console (knotty) UI until the build stops. Which can also result in an unusable build directory. Unless anyone objects I will remove the Force Stop option. It seems right that the UI will protect the user from being unable to use it next run. I think that's a much clearer approach by removing the "force stop" Be aware that this means the build won't actually be stopped until all of the running tasks have ended. If that's a long task like packaging the kernel you may be waiting some time. This is what I added the Force Stop option in the first place. We could possibly add a two phased Stop -> (optional) Force Stop for the impatient but I suppose we'd want to add large warnings if we did that. I've developed a patch which leaves both Stop and Force Stop but explains them both and their ramifications. verify the bug with commit 46cf540e63a848512617b20fd8492f81bfb2f704, it's fixed. |