Thanx again - see revised post, hope ok. You should be seeing a cup of coffee.

(Pls check: Link on Patreon "go back to Scott Molinari’s Page is broken, gets 404)

Thanks for your prompt response, Scott. I added the this. parameter among the many things tried to resolve the problem; sorry not to remove it prior to the post.
However, removing the “this.” does not clear the “missing value” problem. How should the name parameter be set - is it required for the carousel? What I am thinking is take the Autoplay example [or one with captions] in QCarousel doco and implement it with the v-for construct; alternatively, could this thread be removed and replaced with the code that would apply to that demo? I think something needs to be done in the forum to get rid of old material and net-out the answers. Thanks for any assistance.

(Revised Post with Answer): Using QCarousel with the v-for iteration was giving me problems - which were solved thanks to Scott Molineri with following link:
https://codepen.io/smolinari/pen/VwZOBYx?editors=1010 << Thank you, Scott - worth a cup of coffee!
A look at this simple fix, no need to read the whole thread (I had thought v-model was not needed):

<!–
Forked from:
https://quasar.dev/vue-components/carousel#Example--Image-slides
–>
<div id=“q-app”>
<div class=“q-pa-md”>
<q-carousel
animated
v-model=“slide”
arrows
navigation
infinite
>
<q-carousel-slide v-for=“slide in slides”:key=“slide.id”:name=“slide.id” :img-src=“slide.url” ></q-carousel-slide>
</q-carousel>
</div>
</div>
Script:
const slides = [
{
id: 1,
url: ‘https://cdn.quasar.dev/img/mountains.jpg’
},
{
id: 2,
url: ‘https://cdn.quasar.dev/img/parallax1.jpg’
}
]
And add to data:
data () {
return {
slide: 1,
slides
}
}

QPdfViewer is a great module, thanks. When added to the application, however, a large number of files were added to the statics folder. Can these be safely removed - which items within statics are required, and which can be deleted? Thanks

In case others run into the problem mentioned above, I changed package.json “@quasar/app”: “^1.0.0-beta.0”, to 1.1.2 and it is working. Note, however, that a large number of files have been added to statics/pdfjs - and it is not clear what these are for, nor if all are required. Request discussion of the pdfjs folder contents and their use. Thanks. (one last request: Can the zoom level be set upon load of the document?)

This looks like a very nice package. However, I am getting the following error message that I cannot track down:
app:extension(index) ️ Extension(@quasar/qpdfviewer): is not compatible with @quasar/app v1.0.0-rc.7. Required version: ^1.0.0 +3ms

@s-molinari Scott - thanks for your reply. I’ll mull over and get back in the coming days. Best wishes with m8a.

This is really a nice helper application - Thanks and congratulations. I got it working but instructions on how to use and tailor the inputs (several inputs per row, for instance) would be helpful. Also, a button to output the vue code for the input fields created. I was not able to see much (anything) on the console until I added my own output commands. A little help on this could make it an app I would certainly pay a bit to use. Other examples of nice form templates using Quasar would be appreciated.

I am having trouble finding examples of binding to sub-component with v-bind, and searching for :propName yields nothing. Any pointers would be appreciated. Simply want to pass two integers one-way to a sub-component and this has proven to be difficult.

Thank you for tackling this objective, as I was curious as to whether Nuxt.js and Quasar combine beneficially. However, I would appreciate an explanation of what the benefits are for doing this. Already we have a huge amount of stuff involved (Node, Vue, Vuex, Quasar) so adding one more package seems like a bad idea unless there are sufficient benefits. If there ae, this combined package could then become a “best practices” approach, with broader support and examples of implementation, possibly some further streamlining.