Loading plugin can not be hidden
See original GitHub issueHi Team
I show a loading with Loading plugin, but I can not hide it, quasar version is 1.1.2, but it works fine with version 1.1.0, my code is :
import { Loading, QSpinnerTail } from 'quasar'
let loading = {}
let lastRequest = new Date(2019);
loading.show = function(config) {
let now = new Date();
let ms = now - lastRequest;
lastRequest = now;
if (ms > 2000) {
Loading.show({
spinner: QSpinnerTail,
message: '',
messageColor: 'white',
spinnerSize: 100,
spinnerColor: 'white',
customClass: ''
})
}
}
loading.hide = function() {
setTimeout(() => {
if (Loading.isActive) {
Loading.hide()
}
}, 1000)
}
export default loading;
Please advise
Thanks
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:9 (2 by maintainers)
Top Results From Across the Web
KOMPLETE KONTROL Error Message: "Could not load plug ...
In this video, we explain what to do if you receive the " Could not load plug -in" error when attempting to load...
Read more >KOMPLETE KONTROL Error Message: "Loading Issue - Plug ...
Symptom. When loading a Preset from the KOMPLETE KONTROL Browser you may receive the following error message: Loading Issue: Plug-in not found.
Read more >Loading Plugin - Quasar Framework
Please remember that calling Loading.hide() with no parameters will hide all the groups. So if you use groups, you may want to always...
Read more >Plugin Loader - Steam Workshop
This plugin allows easy installation and loading of client plugins from multiple different kinds of sources. A plugin is basically an unrestricted mod...
Read more >Fatal error plugin conflict | WordPress.org
Getting a fatal error when activating this plugin alongside wps-hide-login. It only started occurring recently, but have been using both plugins ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

Found the problem! “Loading” was not specified in the plugins section of quasar.conf.js. Apparently that didn’t stop it from working (afaik) in 1.1.0, but it does in 1.1.2. Simply adding “Loading” in the plugins list fixed the issue for me. @aiwarzheng is this your problem too?
@kpwbo Yes, the problem was solved when added “Loading” in the plugins list, thanks guys