No More Posting New Topics!

If you have a question or an issue, please start a thread in our Github Discussions Forum.
This forum is closed for new threads/ topics.

Navigation

    Quasar Framework

    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    1. Home
    2. quem
    • Profile
    • Following 0
    • Followers 0
    • Topics 1
    • Posts 3
    • Best 0
    • Groups 0

    quem

    @quem

    0
    Reputation
    148
    Profile views
    3
    Posts
    0
    Followers
    0
    Following
    Joined Last Online

    quem Follow

    Latest posts made by quem

    • RE: [SOLVED] Unable to create compo:Toast but Alert works fine

      Thanks for the help. Indeed, calling Toast.create in mounted() breaks somehow the component and cannot be used elsewhere afterward.

      The above solution works (corrected, use “process.nextTick”)

      mounted() {
        process.nextTick(() => {
          Toast.create('Hello World')
        }
      }
      

      Isn’t there a more elegant solution ?
      When the component is called, I want to perform some checks and display a Toast if needed. I thought mounted() was the good call.
      I know, this question is more about VueJS than quasar finally.

      posted in Help
      quem
      quem
    • [SOLVED] Unable to create compo:Toast but Alert works fine

      Hello there, new to Quasar and I find it awesome !

      I am not able to create a basic Toast which is odd.

      • Created a fresh quasar repo
      • Edited “src/components/Hello.vue”
        – Import { […], Toast } from ‘quasar’
        – Added in the mounted () method the following :
        Toast.create(‘Hello World’) or Toast.create({ html: ‘Hello World’ })

      Nothing appears and the vue developer tool (chrome) doesn’t show anything in Vue instance Root …
      There is no error in the console.

      I noticed that Alert({ html: ‘Hello World’ }) worked fine.

      So my question is : is there something I should specify (e.g in the Layout ?) so Toast appears ? I didn’t find anything in the documentation.
      Thanks for your help

      posted in Help
      quem
      quem
    • RE: Running 'quasar dev' does nothing? (on freshly installed default starter kit) [solved]

      I also had trouble running quasar for the 1st time, using Windows 10.
      command : quasar dev
      Nothing was displayed. http://localhost:8080 got the message “connection rejected”.

      Using command : npm run dev mat
      I figured out I had the error “Error: spawn cmd ENOENT” => Verify that your local variable PATH contains “C:\Windows\System32”, reboot if necessary.
      If it’s still not working, change server port (/config/index.js), as explained above.

      Hope it can help someone.

      posted in Help
      quem
      quem