Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

When updating the progress bar while loading the package list, get the length of the number of packages we need to load minus 1 or maybe 2, and use that many zeroes after a 1 so it scales better if the total number is larger than what I already accounted for so it doesn't update the UI as often. #170

Open
DrewNaylor opened this issue Jun 20, 2023 · 1 comment

Comments

@DrewNaylor
Copy link
Owner

May help a bit. Perhaps this should be applied to the extraction window, too?

@DrewNaylor DrewNaylor changed the title When updating the progress bar while loading the package list, get the length of the number of packages we need to load minus 1 or maybe 2, and use that many zeroes after a 1 so it scales better if the total number is larger than what I accounted for so it doesn't update the UI as often. When updating the progress bar while loading the package list, get the length of the number of packages we need to load minus 1 or maybe 2, and use that many zeroes after a 1 so it scales better if the total number is larger than what I already accounted for so it doesn't update the UI as often. Jun 20, 2023
@DrewNaylor
Copy link
Owner Author

Probably would have to ensure we sync the threads or something when updating the progress bar so there's no race condition. Delegates would be necessary to prevent cross-thread issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant