Comment 6 for bug 1861068

This is an excellent suggestion, and my plan is to add such a feature in a new version of Cubic.

There are some complicities in the user interface, because Cubic is a multi threaded application. To the user, the application seems simple and linear (click next or back buttons), but managing multiple threads to make things seem simple is indeed a challenge.

Cubic’s current “wizard” framework was developed when there were less features, an the intention was that errors would be shown immediately under the progress bars (if possible). As cubic evolved, som processing work needed to be done “between” the pages.

The error you experienced is an example of this, where Cubic attempts to figure out the right kernels to display while transitioning “between” the Terminal page and the Options page.

I am working on a new framework that would allow more easily adding additional pages. This way, we can add a page to show the processing progress as we calculate the kernels, the list of manifest packages, the boot Giles, the preseeded filed, etc.

With the ability to add new pages more easily to the UI, we can also insert a general error page, to make it easier for the user to know when things didn’t work out.

Finally, I’m very interested in errors that you encounter, in addition to this one. So please do report them!