Tweaking the Dashboards for non-matched group sizes


The default settings for the "widgets" (buttons?) in the SITE part.

There are settings for the 1x1 widget,
Widget spacing,
Group spacing,
Group padding.

If "you" edit the size of some/any of these, it can cause alignment problems with groups.

Is there an easy (any?) way of adjusting for the misalignment of the adjacent groups?

I would send a picture/screen shot, but my dashboard is "work in progress" just now with some new things, so the problem isn't there.



no - you just have to play with the spacings until you get it right.



But the spacing is for the entire page - right?

In my example (which you can't see just now) I have three TEXT nodes and a TOGGLE node.
The settings are pulled back to as close as possible to small.

42 pixles for widget size,
2 for spacing
Group padding is 0
and group spacing is 2

Beside that is a group and when shown there is a big enough difference in their height it is not nice.

Any groups which wrap around from the end of the screen are bumped because of the size difference.

So I see that as a possible problem for people in the future (as it will be for me) because of the different vertical sizes.

IF interested, I can send in a screen grab once this other project is completed.

Bah, here it is.
Though only in part.



One of way to resolve this is using CSS to control the height and width of the group. For example, I have a tab titled Dashboard with a group called Light, using the ui_template I modify the height using CSS like this

#Dashboard_Lights {

hope this it helps.


It does help, I am only "putting it on the table" because many new people (like me) don't have these tricks up their sleeves.

When they are designing a web page, they want a .... (can't think of the RIGHT word) easy? way to do it. I don't want to confuse easy and simple.

Rather than having to get a TEMPLATE node and add CSS - which could be beyond them - have a NODE that adds padding and all you do is add the size?

Just a thought.

Yes, I admit that is (basically) what you said, but again: rather than having to get the TEMPLATE node, there is an easier way.