@danielcoliev , thank you for suggestion. But which of the above options would be more preferable for performance and maybe other reasons?

@stukki, thank you - exactly what I needed!

I’m trying to initiate/stop ‘Loading’ or display ‘Notify’ messages right in Vuex upon updating certain properties or upon receiving certain responses from axios rather than repeat the same code in multiple components. What’s the correct way to import these Quasar plugins in Vuex?

Thank you.

The color of the radio or checkbox icons in Option Group component changes accordingly to dark or light, but the color of the labels (text) always remains black. Is that a bug or not? What could be the best remedy ?

With me ‘class=“no-shadow”’ resolved the issue…Is that too straightforward?)

metalsadman,

Thank you for your suggestions, I have tried them all well previously and now I found the issue was that I was using lazy model change with @change event and v-model at the same time. Lazy @change works only without v-model. However, I wanted to render some changes via v-model in real time (like values on q-range labels when moving the slider), and display some elements, like buttons, only on lazy model change. I wonder if such a combination is possible?

I’m trying to show an element on @change event in q-range.
The following doesn’t work:

@change="() => { showButton = true }"

What am I doing wrong? This simple pattern works with @input event. Also, I want to use lazy model change only for displaying the button, but not for the model values rendered in labels or elsewhere.
Thank you.

Datetime component allows to set min and max values for the model thus disabling dates out of the range for the input. However, just the dates but not the time. For instance, if I set ‘min’ time ‘2018-12-02 , 07:00’ and try to pick a time on 2018-12-01 the date will be disabled in the calendar, as it should be. But if I try to pick ‘2018-12-02 , 06:00’ , which is out of the range, hour and minute pickers would still be clickable and the click results in an input event but setting the model to the ‘min’ time, 7:00 in my example.
Is there a way to capture the click on a time out of the range and capture the exact time the user is attempting to input before it got corrected?

I think in certain cases users may need an additional explanation why they cannot pick the time they want (no problem with the date). Otherwise, such behavior of time picker looks queer or even as an interface bug. So it’s necessary to access the event of correcting the input time so that it fits the range.

Hawkeye64, only that I wasn’t creating a separate method to built image path, I was doing that in HTML. However, looks like I found the cause. The images.id was a number and :image="‘statics/faces/’+images.id+’.jpg’", the syntax I used, didn’t convert it into a string.