You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In some cases, module creators may be executing large scale operations in Foundry, and it would be useful to be able to display a progress bar to let the user know how the operation is progressing. Extending this further to supporting multiple progress bars would perhaps be useful as well, so that the progress of multiple operations can be communicated.
User Experience
A module would instantiate a ProgressBar class, which would create a progress bar that's displayed at the top of the canvas, in addition to any others already there. This class would have simple functions such as setPercentage (accepting a single percentage value) and setPercentageFromTotal (accepting current value and total value).
If a class such as this would be out of scope, a simple static interface would also suffice, though one could argue that the interface in place (however "private") captures the feature already.
Priority/Importance
Low. This interface is a definite low priority as it might be useful for only a small demographic of module creators.
The text was updated successfully, but these errors were encountered:
Originally in GitLab by @adamoresten
Feature Summary
In some cases, module creators may be executing large scale operations in Foundry, and it would be useful to be able to display a progress bar to let the user know how the operation is progressing. Extending this further to supporting multiple progress bars would perhaps be useful as well, so that the progress of multiple operations can be communicated.
User Experience
A module would instantiate a
ProgressBar
class, which would create a progress bar that's displayed at the top of the canvas, in addition to any others already there. This class would have simple functions such assetPercentage
(accepting a single percentage value) andsetPercentageFromTotal
(accepting current value and total value).If a class such as this would be out of scope, a simple static interface would also suffice, though one could argue that the interface in place (however "private") captures the feature already.
Priority/Importance
Low. This interface is a definite low priority as it might be useful for only a small demographic of module creators.
The text was updated successfully, but these errors were encountered: