#1128 Show first 10 projects that failed to load when loading a workspace

[Andrew Cottrell]

If you are running C::B in batch mode the dialog that pops up if a project in the workspace has failed to load does not show which project failed and refers you to the log, which when using the batch mode is not very helpful IMHO.
It would be allot nicer for the end user to show which projects failed to load in the pop up (limited to say the first 10). This will allow the end user to see the projects that failed and not have to look at the log in the vast majority of cases.

[Teodor Petrov]

1. Showing UI messages in batch mode is wrong. It must not happen. Some people want to use cb batch in CI build, so showing UI messages, breaks those.
2. If the info is not present in the log it should be added.

[Andrew Cottrell]

Before going off on a tangent you need to understand the existing code and what it does as it currently shows a few dialogs in batch mode.

As for 2) you try to build the github code via the batch mode and come back and let me know if the error message in the pop up is useful.

For this and most of the other changes I do "Think about an end user trying to use the existing C::B functionality and I think that making the changes will make it easier for the end user to use C::B".

I am starting to get the hint you do not care about usability.

[Teodor Petrov]

Before going off on a tangent you need to understand the existing code and what it does as it currently shows a few dialogs in batch mode.

If the existing code shows message boxes in batch, it is wrong and broken, already.

As for 2) you try to build the github code via the batch mode and come back and let me know if the error message in the pop up is useful.

Showing messages for CI/batch builds is wrong because the executable gets stuck waiting for someone to press the button.

For this and most of the other changes I do "Think about an end user trying to use the existing C::B functionality and I think that making the changes will make it easier for the end user to use C::B".

Probably you're correct for you, but I have a bigger picture in my head. Showing messages in batch is the major reason I've abandoned making CI builds for Windows. Debugging thing like this is a nightmare.

I am starting to get the hint you do not care about usability.

I suppose we have different understanding about term usability. Which is probably fine.

[Andrew Cottrell]

Attached is a patch that shows the first 10 failures and the project names instead of just the failure number.

The CI changes are NOT part of this ticket as this is to help end users.