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. Tags
    3. q-select
    Log in to post
    • T

      @input not trigger when changing the value of model q-select
      Help • q-select quasar reactivity • • thekingrenz23

      3
      0
      Votes
      3
      Posts
      1567
      Views

      T

      @dobbel thanks a lot for the explanation and tips on how to solve it

    • C

      How to prevent q-select to clear user value when out of focus?
      Help • q-select • • cloudm

      4
      0
      Votes
      4
      Posts
      2339
      Views

      D

      @cloudm Thanks for posting your solution - it still isn’t quite preferable in my case because the input value is sharing a binding with the model used for the selection. Ideally the input would have a separate v-model so that you could use-chips and use multiple (sounds like a potential Vue 3 feature?). For the time being I think the input/menu is still a pretty good workaround (I am using it for an @mentions type feature).

    • W

      QSelect with multiple option-label
      Help • option-label q-select • • wyepez

      1
      0
      Votes
      1
      Posts
      234
      Views

      No one has replied

    • R

      q-select not displaying drop down
      Help • dropdown issue list q-select • • Rohit

      1
      -1
      Votes
      1
      Posts
      239
      Views

      No one has replied

    • F

      q-select auto complete not updating use-input value and can not hide it
      Framework • q-select • • firibz

      1
      0
      Votes
      1
      Posts
      161
      Views

      No one has replied

    • V

      [v1] QSelect is a downgrade
      Framework • q-select • • vuras

      9
      2
      Votes
      9
      Posts
      494
      Views

      G

      I also think QSelect in 1.0 is somewhat a downgrade. Somehow it doesn’t behave well and is more difficult to use. It feels like 0.17 popups behaved more consistently (looked more professionally), there were options with enabling checkboxes and a relatively simple search, and the entire api was simpler to use.

      It would be nice if somehow a reincarnation of 0.17 QSelect was included to 1.x under a different name (QSimpleSelect?), and I’d be even willing to pay for this feature.

    • haigha-earwicket

      Possible to detect q-select options change?
      Framework • model q-select • • haigha-earwicket

      4
      0
      Votes
      4
      Posts
      1162
      Views

      haigha-earwicket

      @metalsadman ok, I had no idea you could set a watcher on a computed property!

      watch: { 'computedOptionsB': function (value) { if (value.length === 1) { this.model.b = value[0].value } } }

      and this allowed me to return my computed property to a no-side effects mode:

      computedOptionsB() { return options.b.filter(o => matchFilterKey(o.filterKey, this.model, 1)) },

      Thanks!

    • A

      Add /Extend q-select auto self-filter prop ( similar to default v0.17 ) ?
      Useful Tips (NEW) • q-select • • amex

      3
      0
      Votes
      3
      Posts
      646
      Views

      A

      @metalsadman .

      Thank you for the example. Took me a while to figure out a few quirks with the q-select props.

      for anyone looking for this … you can check @metalsadman provided sandbox above , he has done all the work . I want to add few comments for beginners like me .

      $ quasar new c BaseSelect your custom extended component from quasar ( here is where we will customize the q-select in my case )
      add index.js to export your component

      import BaseSelect from './BaseSelect.vue' export { BaseSelect }

      next mount it to your vue boot
      $ quasar new b base-select
      register the component in your new boot file

      import * as BaseComponents from 'components' // leave the export, even if you don't use it export default async ({ app, router, Vue }) => { // Globally register the components Object.keys(BaseComponents).map(v => { Vue.component(v, BaseComponents[v]) }) }

      final step is to go to your quasar.conf.js and add this boot file ( named in quasar new b xxx ) in the boot list array .
      for q-select>> Few things i run into is to notice or take care ( not to mix multiple prop , on a string data model for q-select) ,
      This way is more expressive and saves lots of time if you need to use the same props over and over again .

    • M

      QSelect option-value not setting to specific property, but entire object
      Framework • options q-select v1.0 • • mlarson

      2
      0
      Votes
      2
      Posts
      315
      Views

      M

      Figured out I needed emit-value and map-options

    • S

      q-select with computed property as model
      Help • computed q-select • • sribe

      1
      1
      Votes
      1
      Posts
      1639
      Views

      No one has replied

    • D

      Separators / sections for q-select and q-dialog-select
      Help • q-dialog-select q-select • • dsl101

      6
      0
      Votes
      6
      Posts
      2113
      Views

      s.molinari

      This seem to have worked.

      https://codepen.io/smolinari/pen/MdXyJR

      Scott