dashboard

Hi,

first thanks for this awesome software. But I have some trouble and I don't know how to proceed. First I try to find out what else I could provide for this report to be a good bug report.

First, I use the latest version (v1.14.0) from openSUSE build Service. I know, I should compile it by my self to avoid any other causes for this behavior. But for now I still use this package from there

Describe the Bug

Not sure it this is a bug or was changed intentionally, but after upgrading to v9.12.2, All language v-chip are rendered like this which looks really ugly:

It is affected by a possibly inverted media query which turn labels to block elements instead of `f

Is your enhancement request related to a problem? Please describe.

Clear visual indication when an integration/application is connected/active.

Slack is fully connected and active at this stage. It would be nice to have a visual indicator on this page to know slack is connected without clicking on configure and navigating to another page.

![image](https://user-images.githubuserconte

Most items coming from questions on the community forum

• a proper multicategory bar example based on https://community.plotly.com/t/multicategory-axis-type-example/26392
• example of shape or annotation covering several subplots thanks to xref='paper'. Also the shapes and annotations tutorial should link to each other.
• orthographic projection example in 3d axes tutorial (or

https://vuestic.epicmax.co/admin/ui/notifications

Alert can't be closed because it has not modelValue.

Need to make similar demo like in docs https://vuestic.dev/en/ui-elements/alert#closeable

See this discussion: epicmaxco/vuestic-ui#1626

It would be nice if one could document how the x and y coordinates are defined. (Beginners might not know about it and well the more documentation the better).

What I think when I see x and y:

What it actually is:

It would be useful to be able to toggle/flag into a process-level mode to group by pid and display more process-level information like the full command line.

• For the "Utilization by process name" window, we could group by pid rather than process name so that it's easier to find specific heavy network resource consumers.
• For the "Utilization by connection" window, including the pid + cmdlin