@metalsadman Awesome! This works for me. Thanks alot!
Next time I’ll check the issues, too

I noticed that actually both context menus are opening ontop of each other.
So I think this is a bug.

Is there a way to stop the right-click event and the long-click event (on mobile) on the inner QMenu?
Otherwise I’ll have to work with mouse-enter events or something and disable one menu programatically and hope for a fix

I don’t think this is possible with QCarousel.
And I know it is not what you are looking for, but maybe you could use the thumbnails option: https://quasar.dev/vue-components/carousel#Example--Thumbnails .

If not, you might need to look for another component. For example there is a package called Swiper that can do exactly that. Check out the “Centered Slides” example at https://swiperjs.com/demos/
Personally, I always like to stick with one framework and try to avoid including additional libraries as much as possible (especially when it’s probably overkill compared to QCarousel). But if you really need this, it could be worth it

I’m assuming you are using the img-src prop on the q-carousel-slide component like this:

<q-carousel-slide :name="1" img-src="https://cdn.quasar.dev/img/mountains.jpg" />

You could do this instead to archieve something similar:

<q-carousel-slide name="1" class="q-pa-none">
     <img src="https://cdn.quasar.dev/img/mountains.jpg" alt="mountains" class="fit" style="object-fit: cover;">
</q-carousel-slide>

So that you can add your onerror-listener to the<img> tag yourself.

Note the q-pa-none class on the q-carousel-slide and the q-carousel should probably not have the padding prop

Hi,

I want to have different context menus based on what the user clicked on in a hierarchy of elements.
More precisely, I need a context menu for individual elements and for the background / the container (it’s for a file-explorer).

In Quasar 0.17 I did it like this: https://jsfiddle.net/Lwz8pj34/3/
It works as expected: When I right-click on the container, the parent context menu opens, and when I right-click on the child element, the child context menu shows instead.

But after my v1 upgrade, this doesn’t work anymore, see: https://jsfiddle.net/e71dfcxL/ (version: 1.1.6)
The parent context menu is always opening regardless on which element I click.

Am I doing something wrong?
Or is this maybe a bug?

YES!! @blur THAT’S IT!
Thank you guys so much!

@s-molinari said in How to access/overwrite internal menu component from QSelect?:

How can a multi-select autocomplete offer multiple selections and always stay open?

uhmm… I think we are not talking about the same thing
I am talking about a <q-select> where the attribute multiple is set. Like https://quasar.dev/vue-components/select#The-model see the right example with the label “Multiple”:

1. you click on the QSelect
2. a menu opens
3. you can select an option
4. – the menu stays open –
5. you can select more options

The menu only closes when the user removes focus from the QSelect.
— or when I modify the URL query parameters… which Is what I’m preventing

Sure, I could use a button to trigger the update, but that would be very inconvenient for the users.

@s-molinari for a single-selection that would do it, but I’m actually talking about multiple selection.

Let me re-phrase the base problem:

• I use a QSelect in multi-selection mode as a filter for a table
• The selected options should be reflected in the URL (as query parameters)
• I want the user to be able to select multiple options without having to re-open the QSelect
• Therefore I cannot modify the route while the menu is open
• So I want to do the URL modification as soon as the menu is closed

And that is why I would like to overwrite the internal QMenu that the QSelect is using, because it exposes the showing state.
OR at least properly hook in to the internal QMenu (like in my JSfiddle example, but in a “non-hacky” way)

As a bonus, if I could overwrite it like in the code snipped above, I could implement a more complex menu with nested options, settings and whatnot.
But the main thing is that I need to know when the menu is currently open.

The problem I’m trying to solve:
I’m using a QSelect as a filter for a table and I want the filter to be part of the URL query parameters. But when I modify the route, the page reloads which causes popovers to close. So I need to detect when the user is done selecting (by knowing if the menu is open or not).

And I could accomplish this if I could do something like this:

<q-select ...>
  <template v-slot:menu"> <!-- this slot does not exist -->
     <q-menu @show="onShow" @close="onClose">
         ...
     <q-menu>
  </template>
</q-select>

@s-molinari Well it’s not that it doesn’t work - I need to access the internal QMenu of the QSelect (which it doesn’t expose). The jsfiddle link should show what I’m trying to do