-
Notifications
You must be signed in to change notification settings - Fork 67
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Spacing issue between row name and sub entities #176
Comments
I second this. Maybe a padding option to allow us to reduce the unused area. I've noticed that rows with more than 3 entities are cut from the right unless my browser is running fullscreen, and also leaving off the right-most entities when I'm watching via mobile on the companion app (e.g. as if there were no further entities - no indication that information was cut). |
Yes, in the mobile application, the rightmost objects go beyond the field of the card, which also causes discomfort. |
One more example… I wanted to have four toggles in a single row (related to Adaptive Lighting component). lovelace-multiple-entity-row can do that, but the toggles get cropped to the right, so not all of them are visible. I also tried lovelace-paper-buttons-row, which manages to make all the buttons visible, but they are now ugly buttons instead of nice toggles. Being able to remove the main name (and optionally also the icon) would be awesome for this case. Look: That screenshot was made after adding I can understand |
Should hopefully be fixed by home-assistant/frontend#8369. Manual workaround with card-mod: |
Guys, I saw it again in lovelace, I remembered my problem, I decided to refresh my memory, as I understand it, now the problem still persists, right? And it is in the HA front? |
Is it possible to automatically shift entities to the left closer to the main name if there are more than 3 of them?
For-example, I got it ova here:
If I add anotha sub-entity, in this example this is the lights, this card would be looks like this:
It can be fixed? Thanks.
The text was updated successfully, but these errors were encountered: