@niklaszantner As I wrote on Gitter, you need to rollback Vue package version to 2.3.4, because the new Vue version 2.4.1 breaks Quasar. Everything works fine if you put Vue at previous version.

PS: you need to rollback vue-template-compiler package too (same version).

According to modern device screen sizes and Material Design layout guidelines (https://material.io/guidelines/layout/responsive-ui.html#responsive-ui-breakpoints)
I think it’ll be more correct to have the following breakpoints:

0    <= xs < 600
600  <= sm < 1024
1024 <= md < 1440
1440 <= lg < 1920
1920 <= xl < inf.

What do you think about that @rstoenescu ?
And what about custom breakpoints?

Thanks in advance,
Niccolò

Despite I knew to do not change Quasar code (I made this request indeed), I didn’t understand that app variables ovverride Quasar ones.
So, thank you very much! Now I get what I need!

@rstoenescu it’s unfair, you’re playing with our feelings

Thank you very much! You’re really great!
I’m still new in Vue environment and some behaviors are strange to me, but now I understood completely this problem.
Really appreciate this!

Thank you! I close this, see you at my next doubt

Thanks @s-molinari , I didn’t know you were working on docs… We’ll wait then, many thanks!!

I finally got the point looking at Vue guide reactivity chapter (https://vuejs.org/v2/guide/reactivity.html)
In fact property added after Component initalization are not watched at all.
The best solution is replace the entire error object in that case.

Thank you anyway, I set this as solved.

Hi @kristijan97, if you can’t figure out even viewing source code of Razvan examples ask me, I’ve used that and I think I can help.
I’m trying to leave @rstoenescu some time to work on new release, may be I can do my part.

Hi @rstoenescu, it’s always me.

I figured out how to replicate the error in a simple project, that I could push on a git repo.
Here’s the link: https://github.com/ntaddei/router-test

In order to replicate the error:

1. Go on ‘companies’ menu voice, it’ll load Companies component.
2. Add new Company, insert name/motto (just for fun) and click CREATE button. It will add a new Company and go to Company profile (‘companies/:id’)
3. Go back (browser button works as well)
4. Add another Company
5. You’ll see this time it goes on Company profile then immediately back to companies list.

Hope it’s enough, if you’ll find out what’s going on I’ll really appreciate that.
Thank you very much!

Niccolò

Will you update with new Material Design styles and guidelines?

@rstoenescu Any news about this?

Despite I knew to do not change Quasar code (I made this request indeed), I didn’t understand that app variables ovverride Quasar ones.
So, thank you very much! Now I get what I need!

There are other possibly events, like deleting one per one every letter or delete a single letter. I think it’s not so easy to understand when empty button was clicked.
However, maybe you can find a workaround, but it’s never like doing it natively. I believe that once @rstoenescu is back from his vacation, he’ll be able to add the event listener in a minute.

Cheers

I know that, but this works locally. When I deploy the project and run “npm install” I loose every change made on local quasar code code.
So I need to set breakpoints natively, I don’t need a workaround.

@spectrolite Yes, you’re right! Maybe I’ll take a look to Dialog. Thank you!

I need a custom Modal that behaves like Dialog: it has a determined width but not the height, so it raise until a specified max-height and then begin to scroll. I think that modal-layout is pretty rigidous and often cause wide blank spaces in some screen sizes.

Is it possible @rstoenescu ?

Thanks in advance,
Niccolò

@spectrolite I thought the same thing, but newVal may be '' (empty string) even when I manually delete all the content, because @change will be raised every time I change the search input content.

According to modern device screen sizes and Material Design layout guidelines (https://material.io/guidelines/layout/responsive-ui.html#responsive-ui-breakpoints)
I think it’ll be more correct to have the following breakpoints:

0    <= xs < 600
600  <= sm < 1024
1024 <= md < 1440
1440 <= lg < 1920
1920 <= xl < inf.

What do you think about that @rstoenescu ?
And what about custom breakpoints?

Thanks in advance,
Niccolò

Hi, I’m trying to set min and max property on a dialog input with type='number'.
I’ve set min: 0 and max: 32 but nothing happens when I write a number greater than 32 or less than 0.
This happens both using a model which is an object property and a number like docs example.
Anyone can help?

@rstoenescu @s-molinari