Largely agree with you about the waiting aspect, but in this case, a minimum of visibility would be nice. « Draft a feature request! », we do it and then black box…
Yes, Gladys provides possibilities, notably with MQTT and Node-RED which I use, but some are « restricted » (e.g.: text- or date-type data coming from Node-RED impossible to retrieve…).
Before adding a nice body and options to a car, you have to give it an engine with adequate performance.
Totally agree with @cicoub13
Gladys Plus respects our privacy in every respect; after that, everyone is free to prioritize the features they want to use.
For such a system to work, and to endure, I see only one possibility: funding!
Good evening @Einstein8854, In that case, since you have programming knowledge why not propose a PR with the features you need.
I think you’re not the only one waiting for the development of a specific feature.
With additional developers, that would help improve the engine’s performance as you say…
@Einstein8854 I don’t doubt for a moment that your intentions in your messages are good. The tone, however, leaves something to be desired in my opinion, because everything has been very clear from the start: Gladys is developed mainly by Pierre-Gilles and a few kind contributors (who are not a crowd) who add their bit to the project.
Donc si tu adhères au projet, c’est que tu sais très bien qu’une demande de fonctionnalité requiert 2 choses :
Cela implique parfois des délais et la seule manière de réduire ce délai et la frustration qui peut aller avec, c’est de faire le boulot soi-même.
Je n’arrive pas à comprendre en quoi ton manque d’intérêt pour Gladys Plus t’empêche de travailler sur le développement de la fonctionnalité que tu attends ?
Hi @pierre-gilles,
Can you adjust (reduce) the up/down scroll speed?
On my end, it’s almost unusable as it is:
Great! It’s a pleasure to read 
Yes indeed, I reduced it a bit, can you re-test and tell me if it’s better like this?
( Same url : https://improve-dashboard-reorder-mo.gladys-plus.pages.dev )
I had the same problem and it’s much better. I might reduce it a little more.
PS : new save test without the final scheduling click and it works perfectly.
@tiboys I’ve reduced it again, can you retest and tell me? Thanks for testing!
That seems very good to me like that!
Thanks!
Does the Reorder button still make sense? It’s fine with me as it is, but that would avoid having two different ways of working…
Yes, it makes sense; for me on mobile it’s complicated to reorder when the widgets are fully expanded — this compacts them during reordering.
On desktop, there’s no need for this behavior.
Perfectly perfect ..
It leaves time to schedule the trip wherever we want.
Many thanks
Thanks for your feedback, I’ve merged these improvements into master, they’ll be included in the next Gladys release! 
Hello,
Small UX bug found.
When editing a dashboard and there are more than 10 rooms in the dropdown list of a widget related to a room, the end of that list is hidden by the « cancel/delete/save » bar.
Question: Is it normal that when adding a widget to a dashboard it is always placed in column 1?
Thanks for the feedback @mikael, I’ll take a look!