On 17.08.2017 11:30, Stefan Tauner wrote:
On Thu, 17 Aug 2017 10:23:54 +0100 Richard Hughes hughsient@gmail.com wrote:
On 17 August 2017 at 10:18, Stefan Tauner stefan.tauner@gmx.at wrote:
However, this is inevitable sometimes as explained before... so maybe we need some additional message passing indicating the different reasons for a "change of plans" so that the UI can react? (which is exactly the type of complication I wanted to avoid ;)
I think a status enum of something like RESET would be enough to show something hand-wavey in the UI, e.g. "Sorry for the delay, trying harder..."
Let's call this statement RESET.
Am I the only one seeing a contradiction to what you wrote half an hour ago (below)? Did I miss something?
You might be, see below.
On Thu, 17 Aug 2017 09:58:25 +0100 Richard Hughes hughsient@gmail.com wrote:
If the percentage does go backwards then we need to give the user a really good reason of why, otherwise users *will* file issues and bugs about it.
Let me translate that for you:
A := the percentage does go backwards B := we need to give the user a really good reason
He said A -> B.
Having a RESET enum value allows us to fulfill B, thus:
RESET -> B
which suffices to say:
RESET -> (A -> B)
I don't see a contradiction ;)
Nico