• (cs) in reply to Mike Caron
    Mike Caron:
    dpm:
    I can't think of any clever or even snarky way of pointing out that 1/5 != 0.5
    Let me try:

    "Hmm... 0.5 == 0.2? This must be that 'new math' I keep hearing about..."

    0.5 == 0.2. This is a Microsoft STANDARD... I'm sure of it!

  • Genitus Prime (unregistered) in reply to Dignissim
    Dignissim:
    Kiss me I'm Polish:
    There should be an obligatory UI class at CS courses.

    Q Effing T

    Cutie!?!?

    Anyway, sounds like Microsoft Time to me..

  • gonzo (unregistered) in reply to Severity One

    We'll need an xsd file for that though.

  • AdT (unregistered) in reply to dpm
    dpm:
    I can't think of any clever or even snarky way of pointing out that 1/5 != 0.5

    Maybe they're using radix 25 (dec) math?

  • adamas (unregistered) in reply to kjordan

    LOL 1+1=3 for large values of 1

  • Spudd86 (unregistered) in reply to Kiss me I'm Polish

    There is for me (University of Toronto)

  • Dana (unregistered)

    Apple did this too, in the bootup process for Tiger nonetheless! I'm running Leopard now, and the command mentioned here: http://daringfireball.net/misc/2005/04/tiger_details#waitingforloginwindow. doesn't seem to exist anymore. Perhaps they've just hidden it better.

  • Zeo woods (unregistered)

    Wow, that actually makes pretty good sense dude.

    Lou www.big-brother-watching.net.tc

  • pauls101 (unregistered)

    I once did the same thing but the company didn't like it ("too jerky"), and they wouldn't buy indefinite progress either.

    I then tried increasing the range of the progress bar each time I incremented it, starting at around 50%. That caused the bar to fill asymptotically, never quite reaching the end.

    I added a routine that "completed" the bar in a half second or so once the operation was done. I've seen any number of progress bars that seemed to work that way.

    This worked in my case, but would have to be tuned for individual cases (assuming that the total number of steps could be roughly predicted.) Otherwise the bar would appear to stick.

  • Joshua David (unregistered)

    I found a really funny bug in the file copying window in Windows 95 and maybe Windows 98. If you grabbed the window with your mouse and moved it around, the bar would stop, but worse than that, so did the copy.

    Any non-believer was always amazed when I showed them this.

  • GVOLTT (unregistered)

    So that's what happens when VLC Media Player has to rebuild the font cache...

  • Ryan (unregistered) in reply to Severity One

    Maybe throw in some XPath and XSL transformations. I think we may be getting somewhere!

  • Piripinui (unregistered)

    Does anyone actually believe this is for real?

  • anon (unregistered) in reply to dpm
    dpm:
    I can't think of any clever or even snarky way of pointing out that 1/5 != 0.5

    was hoping someone else saw that! i actually thought i must've been smoking crack this morning when i noticed it!

  • DYo (unregistered)

    I don't see what the BFD is. Read his method comment, that makes sense to me. I couldn't understand the whole problem or tell you if he implemented the right design without seeing what GUI framework you're using and what threads are running, etc.

    It sounds like the beginning of the task is really something that is indeterminate. And the end of the task is linear. So he randomly progresses up to half way for the indeterminate part, and then finishes smoothly/linearly/accurately for the last half. Brilliant! This man needs a beer!

    Btw, I've committed some progress bar sins along the way, including setting up strange sleeps, yields and bizarre threading and paint calls. But I repented.

  • DYo (unregistered) in reply to DYo
    DYo:
    I don't see what the BFD is. Read his method comment, that makes sense to me. I couldn't understand the whole problem or tell you if he implemented the right design without seeing what GUI framework you're using and what threads are running, etc.

    It sounds like the beginning of the task is really something that is indeterminate. And the end of the task is linear. So he randomly progresses up to half way for the indeterminate part, and then finishes smoothly/linearly/accurately for the last half. Brilliant! This man needs a beer!

    Btw, I've committed some progress bar sins along the way, including setting up strange sleeps, yields and bizarre threading and paint calls. But I repented.

    But I should add his implementation had some bugs. Rand generation was weird. Should be something like

    private int rand = 0;
private static final int HALFWAY = 500;
private static final int INCREMENT = 4;
...
rand += Math.randInt(INCREMENT); // return a rand int from 0 to the val passed
rand = rand < HALFWAY? rand : 0;
setProgressValue(rand);
  • DYo (unregistered) in reply to THE Brian
    THE Brian:
    In my last major project, I experimented with a progress bar, but the results were less than spectacular. Instead, I settled on a status bar at the bottom, and I placed meaningful messages ('Querying Database' ...) in it. The users liked that a lot better than the progress bar, and it was helpful when the occasional bug was revealed. ("What was the last status message you saw?")
    Sounds like a security flaw to if this is enterprise software.

Leave a comment on “Meaningless Progression”

Log In or post as a guest

Replying to comment #:

Log Out

« Return to Article