I agree with you: there must be feedback that the action was requested.
I did a bit more testing in our product. When the user starts a debug session in our case build will always happens:
If the Console View is not opened it will opened during the build process.
If the Console View is already opened the it will be cleared first then it will display the building progress.
In all cases after the user request a debug there will be some build progress (scrolling) in the Console View and at the end it will show the build errors in red.
I think that is sufficient feedback.
So it cases like this, does it makes sense to add the “Never” option?
It will not be the default, but if some user like it this way, let it be.
From: platform-debug-dev-bounces@xxxxxxxxxxx [mailto:platform-debug-dev-bounces@xxxxxxxxxxx]
On Behalf Of Teodor Madan
Sent: Friday, March 04, 2016 10:46 AM
To: Eclipse Platform Debug component developers list.
Subject: Re: [platform-debug-dev] Continue Launching if project contains error
It is strange to see no feedback on the requested action. For the other options, user opts for additional tasks on the requested action, but “launch” action by itself will always complete with feeback
One way to show feedback without being too intrusive is to show a mylyn style of notification balloon.
I noticed that the “Run/Debug/Launching” preference “Continue launch if project contains errors” has only “Always” and “Prompt” options, while the other three above it has three options: “Always”, “Never” and “Prompt”.
We have customers that got tired of constantly clicking the “Cancel” button when their project has build errors when they try to debug. They prefer the debugging to give up without a message. That is why I think adding the “Never” option
for that preference will help them.
I was initially surprised when I got this request, because without the dialog how will they know if debugging will never happen. The answer to that is: Debugging will prompt the build and they will always see the errors in the both the
Console View and the Problems View. So that will be enough signal to them that debugging will never happen. So no point of the dialog.
What do you think?
For cases like this should we add the “Never” option in the preference “Continue launch if project contains errors”?