Topics created by MusicForMellons

After using @load for the scroll-element and adding a nextTick it seems to work as should. See this stackoverflow-issue .

@metalsadman Great! Thanks!

See this for a solution and whether that’s how it should be done…: https://github.com/quasarframework/quasar/issues/2033

@rstoenescu said in [15.1] Lazy loading of components: The docs indeed explain code splitting and lazy-loading but don’t mention how the components in quasar.conf.js fit into this picture.

we updated the board… maybe something helped that cheers

I use Vee Validate, it work fine <q-field :error="errors.has('name')" :error-label="errors.first('name')" > <q-input v-validate="rules.name" v-model="form.name" name="name" float-label="Name" /> </q-field> -------- // Data form: { name: '', }, rules: { name: { required: true, }, // Methods submitForm() { this.$validator.validate().then(result => { if (result) { // success }else{ // error }

that set is nice!

Ah, found an example in the quasar template: <q-btn color=“primary” push @click="$router.replace(’/’)" icon-right=“home” > Go home </q-btn>

Ah… it is in the documentation (gloops): http://quasar-framework.org/components/layout.html#Vue-Properties Used this and everything is working brilliantly: <q-layout ref=“layout” :left-breakpoint=0>

Seems like trouble for mapbox-gl. Can you set some breakpoints and see where exactly it fails?

Did you find any solution @MusicForMellons ?

Ok, thanks for the feedback @MusicForMellons! It is definitely pretty spotty based on the browser implementation.

I know this was ages ago, but this will help others too (and lets face it, the docs search engine needs some help too): http://forum.quasar-framework.org/topic/14/add-custom-fonts-to-your-app

Yeah, setting these and adding to class works. Via css setting color to .item > i.item-primary also works. My problem was more of a ‘not working hot-reload thingy’ it seems. Thanks.

Ok! In Pycharm this gives better code support… and it doesn’t harm I suppose.

Works! Thanks!