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
I have 2 scenarios that I have to show for a different loading dialog depending on if a specific class exists with the target element.
Currently, I'm calling it directly like this.
Class not exists: $treeDOM.LoadingOverlay('show');
Class exists: $treeDOM.LoadingOverlay('show', {zIndex: 10});
I wonder if this library supports the listener feature,
like before showing loading view, and after hiding loading view, etc…
Then I can handle the target element in the listener, and let it show different dialog views automatically.
I hope it could be possible.
Thank you!
The text was updated successfully, but these errors were encountered:
Basically you are asking for some events to be fired for the target element when a LoadingOverlay is being shown/hidden, right?
I had thought about that, but then I also thought that this is a pretty simple plugin and you can normally handle those things within the same code you use to show/hide it...
However, this is something it is worth thinking about for the next major version, which is due soon. Since it will radically change the way multiple LoadingOverlays work (instead of increasing a counter, a new one with completely different settings will be shown), it might make sense to include events.
I have 2 scenarios that I have to show for a different loading dialog depending on if a specific class exists with the target element.
Currently, I'm calling it directly like this.
Class not exists:
$treeDOM.LoadingOverlay('show');
Class exists:
$treeDOM.LoadingOverlay('show', {zIndex: 10});
I wonder if this library supports the
listener
feature,like before showing loading view, and after hiding loading view, etc…
Then I can handle the target element in the listener, and let it show different dialog views automatically.
I hope it could be possible.
Thank you!
The text was updated successfully, but these errors were encountered: