Help

• J

  [Solved] Q-toolbar dropdown menu possible ?
  • jctrebalag  

  7
  2
  Votes
  7
  Posts
  2856
  Views

  

  I ended up modifying my approach again slightly to incorporate the ability to include an avatar into the “button”. Specific details are available here: https://forum.quasar-framework.org/topic/2602/image-in-top-dropdown-menu/2 The short of it was to use a q-chip with avatar set to the image and no content – then use the clever popover approach above.
• 

  How can I access vue instance?
  • danielsalles  

  9
  1
  Votes
  9
  Posts
  5063
  Views

  

  @rstoenescu Oh, my bad. I had added in components. Now I’ve got it, and it’s working. Many thanks for the support offered
• 

  Using firebase as plugin in Quasar 0.15
  • CristalT  

  8
  0
  Votes
  8
  Posts
  4568
  Views

  

  The error is not related with repo. Quasar CLI uses yarn to create the project. The node version you have is incompatible with the installed yarn version. As log says, the node version must be “>=4 <=9” I’ve experimented the same error on my local since ago. I recomend you change the node version. If you have nvm, it could be very easy. Then reinstall Yarn and Quasar CLI under new node version selected; 8.9.0 will work. Hope it helps you.
• J

  Using global lodash with quasar v15 (Solved)
  • jeimz173  

  7
  0
  Votes
  7
  Posts
  3597
  Views

  T

  I ended up doing this in my plugin file. This makes it globally available. // import something here import _ from 'lodash'; // leave the export, even if you don't use it export default ({ app, router, Vue }) => { window._ = _; }; And then add globals: { 'ga': true, // Google Analytics 'cordova': true, '$axios': true, '_': true, '__statics': true }, into .eslintrc.js. So the linter doesn’t complain. One has to restart quasar dev to reload the .eslintrc.js file. After that one can use lodash as usual just by typing _.
• A

  Q-Img inside Q-Virtual Scroll
  • altezza04  

  1
  0
  Votes
  1
  Posts
  5
  Views

  No one has replied

• K

  Q-Tree stopped working inside ScrollArea after update
  • kozyyy  

  3
  0
  Votes
  3
  Posts
  7
  Views

  K

  @metalsadman Thank you! Made a little investigation with your code. The problem was in adjusted height for Qscroll element.
• B

  Routes break in production when enabling HTML5 history mode
  • BigAppear  

  13
  0
  Votes
  13
  Posts
  7192
  Views

  G

  @gvorster said in Routes break in production when enabling HTML5 history mode: How can I fix this when testing locally using: quasar build quasar serve dist/spa Only root “/” is working Found it. I need to do quasar serve --history dist/spa Then it is working.
• M

  Trying to upgrade: 'Quasar App Extension "upgrade" is missing'
  • Mar8  

  3
  0
  Votes
  3
  Posts
  13
  Views

  

  if on windows, re-install quasar cli npm i -g @quasar/cli then try again
• T

  Using Quasar components within an App Plugin
  • turigeza  

  5
  0
  Votes
  5
  Posts
  260
  Views

  D

  @metalsadman said in Using Quasar components within an App Plugin: . For anyone who land here like I did, to call Notify this way you have to use the method create like this: Notify.create('message') or Notify.create({message:'message', position:'top'...}) This is equivalent to calling this.$q.notify() from within a component
• D

  unable to load quasar.dev (weekend 10/9,10/10)
  • dgk  

  4
  0
  Votes
  4
  Posts
  38
  Views

  

  @dgk there’s a dns issue in the quasar.dev site, for the meantime use the temp docs site here https://quasardev-ijurxbbaxj.now.sh/
• 

  Custom variables added to quasar.variables.sass seem to be ignored
  • mboeni  

  1
  0
  Votes
  1
  Posts
  9
  Views

  No one has replied

• A

  Error: Caccont find name 'process'
  • Abstauber  

  1
  0
  Votes
  1
  Posts
  9
  Views

  No one has replied

• D

  no dev or build property under script property in package json is that correct ? How do I launch my app in browser
  • dsahoo  

  4
  0
  Votes
  4
  Posts
  12
  Views

  

  @dsahoo post your quasar info you’re probably missing a dep.
• F

  q-select change q-chips bg and text color when multiple is used.
  • Fedack  

  12
  0
  Votes
  12
  Posts
  51
  Views

  F

  Oh, I completely agree, you can’t cover every bases. But this is the first thing you see, it’s the main label color. I do think it should be easy to modify using props since you can change the color of the focus, why not change the color of the unfocused one? But anyways, just a suggestion. @s-molinari Thank you for your time
• E

  Typescript errors
  • Emptyless  

  3
  0
  Votes
  3
  Posts
  459
  Views

  W

  hi it is old, but i am getting still this error. how did you solve this and where did you set the config, in which line?
• R

  I can't focus my q-input...
  • Raph  

  5
  0
  Votes
  5
  Posts
  89
  Views

  

  @Raph @dnix try it with $el. Ie this.$refs.someref.$el.focus().
• V

  Help with spacing rows
  • VerumLudens  

  2
  0
  Votes
  2
  Posts
  23
  Views

  C

  remove <q-space></q-space> because it does nothing in your case (it is only for horizontal gaps, I think) add the class q-gutter-y-xl to the div in line 2 Explanation: That div contains three elements (two divs and the <hr>) which you want to space out. Whenever you want to add equal spacing between all elements, using a q-gutter class on the container does the trick (except when working with cols, then it’s q-col-gutter, see https://quasar.dev/layout/grid/gutter). (Alternatively, you could manually add margins to your rows or the separator, for example q-my-xl on the <hr> or the divs, but the gutter method is better) Also, consider replacing <hr> with <q-separator />.
• B

  CSS adjustments for IE11
  • bitman  

  1
  0
  Votes
  1
  Posts
  9
  Views

  No one has replied

• T

  Dynamic v-model bindings in input fields do not update visually
  • tonyskulk  

  25
  1
  Votes
  25
  Posts
  165
  Views

  

  @kowy said in Dynamic v-model bindings in input fields do not update visually: I have the same problem with q-input. I have tried to dynamically create a set of q-inputs as @tonyskulk did. And the same result. The underlying model changes but, visually the value of q-input returns back just after focus out of the q-input. quasar - 1.1.0 @quasar/app - 1.0.6 @quasar/extras - 1.3.1 vue - 2.6.10 you need to set a key if you are using v-for’s. otherwise make a codepen.
• S

  Q-Tree How to tick all nodes
  • ScoutKirkOlson  

  4
  0
  Votes
  4
  Posts
  22
  Views

  S

  @chyde90 works like a charm, thanks!