@Mak-NOAA you can make use of the header slot and customize how your q-th’s look then use the sort method of q-table. Check api cards https://quasar.dev/vue-components/table#QTable-API scope slots and methods section. Haven’t done this myself*

By overriding default scoped slot, header in your case, you will have to implement the qtr an qth.
Ie.

<tem... slot:header ...>
 <q-tr ...>
    <q-th ...>
      <q-tooltip>...</q-tooltip>
    </q-th>
....
....

Sry im on my phone, just showing above how your temp structure would look like.

@jhon said in get a reference to the instance of the application:

Hello
I am new with quasar, it is possible to get a reference to the instance of the application from the router.js ( if (THIS.$ability.can(m)){ )

router.afterEach ((to, from) => {
         const canNavigate = to.matched.some (route => {
             for (var meta in route.meta) {
                     if (THIS.$ability.can (meta)) {
                         return true
                     }
                 }
                 return false
             } else {
                return true
             }
         })

Assuming your ability is initialised as a vue prototype in a boot file, then you can get it using Vue.prototype.$ability.can(...).

@janviehweger you gave it a string value just stack-label is enough to set it or if voltage is a boolean data model, :stack-label="voltage", with a colon :.

@jelices the author can change it i think.

@Stanley said in [V1] Q-Card Layout Issue:

@metalsadman Thanks! I found they are now with the same width. I would like, for example, the first card occupies 200px, the second one occupies 200px, and the third one occupies the remaining 100px because I set the max width 500px in the parent. Could you please have a look again?

updated https://codepen.io/metalsadman/pen/wVBMvw

@Stanley add a no-wrap class on your parent div wrapping the cards. https://codepen.io/metalsadman/pen/wVBMvw

@jpsala said in Exit app in android:

it’s strange that it’s working in the emulator but you are right, I’ll try to refactor so to use the navigator object after returning from the action, or something like that

see update above.

@jpsala yep, i guess that resides in your action something js. try using mapActions in your vue into that file, see if it gets navigator context, otherwise you’ll have to transfer that logic in your view. or you could pass the navigator itself as payload to your action.
ie.

// in your vue file
this.$store.dispatch('logout', navigator)
// in your action
logout({ commit, dispatch }, navigator) {
...

@jpsala you probably don’t have navigator available from where you called that logout action of yours.