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
A listing page, where all data needs to be coming from an api call.
In this case, we can just pass isLoading = true and loadingWidget = {Component} to The BisqScaffold/BisqLayout classes and they take care of rendering the given component in the mid of the screen till the data arrives.
Scenario 2:
A form page, where all controls can be rendered initially with empty fields,
An overlay loader can be shown with blurred background so the form/controls are visible in the background, but cannot be interacted with
Once the data arrives, overlay loader is removed and the form is populated with actual data.
Even to achieve this, we set only isLoading = true to The BisqScaffold/BisqLayout classes. Without setting loadingWidget when isLoading is set to true, they show the overlay loader.
The text was updated successfully, but these errors were encountered:
I've just checked, this can be considered fix by using the component CircularLoadingImage by passing the right drawable and true to the loading effect, right?
@nostrbuddha I think this can be considered done, is just a matter of applying it everywhere is needed in combination with the "is interactive" flag to block the UI whilst loading
Loading spinners are needed in 2 ways:
Scenario 1:
Scenario 2:
Even to achieve this, we set only isLoading = true to The BisqScaffold/BisqLayout classes. Without setting loadingWidget when isLoading is set to true, they show the overlay loader.
The text was updated successfully, but these errors were encountered: