Hello everyone,

Is it me or is it the QSelect is a downgrade for the casual use of the component?

I know that now it is more customizable, but for the casual use, older QSelect was so much easier and intuitive to use. You just put the options and that’s it.

There is a lot of props you have to remember. Filtering is a nightmare now, you need to write and mixin a simple filtering function everywhere. The filtering CSS of the field is fucked up also, input is added after the selection, and if the selection is long, then the height of the component doubles and the design of the page is distorted.

Sublabel is removed also which makes you customize every select for just a single sublabel.

What thoughts do you have, guys?

Hello, maybe there is an approximate release date scheduled?

I mean that usage is overcomplicated now. Some useful features was removed and it is left for the user to reproduce it again in favor of customizability? I am not angry or anything, I just think it is kind of messed up now.

Hello everyone,

Is it me or is it the QSelect is a downgrade for the casual use of the component?

I know that now it is more customizable, but for the casual use, older QSelect was so much easier and intuitive to use. You just put the options and that’s it.

There is a lot of props you have to remember. Filtering is a nightmare now, you need to write and mixin a simple filtering function everywhere. The filtering CSS of the field is fucked up also, input is added after the selection, and if the selection is long, then the height of the component doubles and the design of the page is distorted.

Sublabel is removed also which makes you customize every select for just a single sublabel.

What thoughts do you have, guys?

Hello, maybe there is an approximate release date scheduled?

Looks like last two columns were set as sticky. After I made it non sticky, problem disappeared. So IMHO it’s a bug with sticky columns.

Hello,

is it somehow possible to make rowHeight flexible to the content in a row?
I want to put progress bars in my datatable, and every row can have 0-infinity progress bars.
So the problem is that when rowheight is static, datatable is rendered incorrectly.