Want to be honest here, my real pet peeve is that it shows 100%. Ever. At all. Let alone when it hangs there… That’s just insulting.
If it is 100% complete, I should not be waiting for anything. If I were ever developing an operating system I would never allow for 100% to display on a progress bar. 100% means it’s done. We advance to the next screen. Do not display it. It makes no sense.
I do often desire a “click to continue” option, especially helpful for asynchronous tasks. Start a render, and when you get back it says 100% without you having to look at the output folder, for instance. I get what you mean though, it certainly should say 100% unless it’s totally donezo. Probably lazy rounding errors in some cases (Microsoft products are the worst at showing accurate progress bars)
Oh for sure! Not trying to get on your back, just agreeing from a UI developers pov :) I seem to have misunderstood your original intent but we’re saying the same stuff I think
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !piracy@lemmy.dbzer0.com
⚓ Dedicated to the discussion of digital piracy, including ethical problems and legal advancements.
Want to be honest here, my real pet peeve is that it shows 100%. Ever. At all. Let alone when it hangs there… That’s just insulting.
If it is 100% complete, I should not be waiting for anything. If I were ever developing an operating system I would never allow for 100% to display on a progress bar. 100% means it’s done. We advance to the next screen. Do not display it. It makes no sense.
Im 101% done with 100% progress bars
maybe display it for the user for half a second. but nothing else.
my3d printer does this on long prints too, it’ll say 100% for up to 10 minutes when it’s a really long print. makes no goddamn sense.
probably rounding shit in the software and a lack of care on the manufacturer’s side.
I’m just saying that in the world of zeros and ones, a one should never be a zero.
I like this saying. I’m going to steal it. It’s mine now.
imadethis.gif
I do often desire a “click to continue” option, especially helpful for asynchronous tasks. Start a render, and when you get back it says 100% without you having to look at the output folder, for instance. I get what you mean though, it certainly should say 100% unless it’s totally donezo. Probably lazy rounding errors in some cases (Microsoft products are the worst at showing accurate progress bars)
I would say a click to continue screen would count as a next screen in the context of what I’m talking about.
I guess I should have been more clear as to say, it should never say 100%, and still be in the loading loop.
Oh for sure! Not trying to get on your back, just agreeing from a UI developers pov :) I seem to have misunderstood your original intent but we’re saying the same stuff I think