Not all code lends itself and makes sense to run a progress bar. Then you look at your code and determine if the progress is predictable and makes sense to show an incrementing bar - it may not. IMO but the first step is to make the Progress Bar itself, and create a small Sub or Function that can be called on demand which:ġ) either Shows or Hides the progress barģ) displays the % width of the bar control itselfĪnd can be called like ShowProgress(True, "Processing". A slight "variation" of that same thing would be a "known" number of tasks (i.e., your code is going to do Thing1, then Thing2, then Thing3), and you update the Progress Bar to show 0, 30%, whatever, during it. I would hazard a guess that is probably the most common approach dependency as it makes the most sense. Click to expand.Why don't you explain to us, WHAT your code does and how it runs, and explain specifically what would be the logic in your code that would tell any Progress Bar what percent complete, to show? That way we don't have to guess.įor example, the link I posted contains a progress bar approach that depends on a known number of Loop iterations.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |