@beets Wow, it’s fantastic! I learned a lot. Actually, before seeing your reply, I also solved how to deal with recursive call. See this link: https://codesandbox.io/s/eloquent-frost-8vquu But I don’t know what’s the disadvantage of my way, could you please evaluate it? 1). From your step 1 to 3, I register my global component in file “/router/index.js”. Is this ok? 2). For step 4, it’s great I like this way because it’s more like of quasar way. Just one question how it exit recursive call? As you can see my file “search-help.vue” line 43, I add the “v-if” condition to exit the recursive call. Thank you so much!

@atlithor It’s related to the app’s language you set in the quasar.conf file. It will use the corresponding i18n language file(provided by Quasar) to lookup the translation.

@Sfinx i’m sorry if i mix things up. I’m really not that skilled with Docker, that is why i use Lando as it takes care of all this. Just had to figure out how Lando wants me to do Axios calls in different situations.

Simply scroll-target=“body” on your eg : <q-infinite-scroll scroll-target=“body” … />

@acros Here’s a codepen https://codepen.io/ontwikkelfabriek/pen/ExgagbB I used this demo: https://quasar.dev/vue-components/table#Body-slots

@walfin does not seem possible with soly beforeRouteUpdate , but you could store a value in for example vuex before you execute: router.push, router.back, ect. Then you’ll get something like this in the vuex: state: { routeMethod: “router.push”} ,

@codethirsty Here’s a codepen demo for the text color: https://codepen.io/ontwikkelfabriek/pen/dypPpob Here’s a codepen demo for the button: https://codepen.io/ontwikkelfabriek/pen/wvzBzGd

Any chance to fix https://github.com/quasarframework/quasar-ui-qwindow/issues/17 ? It is just appears that adding height to QWindow adds infinite vertical scroll to Quasar projects. Minimal reproduce code is: <q-window :height=“640” />

@Pedro use search function in this forum, https://forum.quasar-framework.org/topic/6135/passing-more-information-and-or-event-from-q-select-on-change-input/3

@flba I answered (today) on Discord, but yes, this sounds like a good idea. Did you add a Github issue on the repo?

yes, the plugin. I’ll try your suggestion, Thanks!

Having the same issues with the same stack. Were you able to fix it?

Many thanks !!

@dobbel https://en.wikipedia.org/wiki/Lotka–Volterra_equations

@aislan - Sorry. Quasar won’t be working with Vite. Scott

Hi all, I have the same problem, here is a codepen: https://codepen.io/alexanderkoehn/pen/poEorwx The curious thing is: When there is an additional normal input or a second q-input, everything works as expected. Using only a <input /> works too. Regards

Thanks for help, I use ts, so I’ve altered @dobbel snipped to watch(() => context.root.$route.params.id, (first, second) => { strategyCode.value = first }); Component uses a new id without any other coding, amazing.