# Proper way of working with lines in groups? **URL:** \ **Category:** Ignition\ **Created:** [June 21, 2016, 3:53pm UTC](https://forum.inductiveautomation.com/t/proper-way-of-working-with-lines-in-groups/11839 "2016-06-21T15:53:55Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![abishur](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/abishur/32/9096_2.png) [@abishur](https://forum.inductiveautomation.com/u/abishur)\ **Post date:** [June 21, 2016, 3:53pm UTC](https://forum.inductiveautomation.com/t/proper-way-of-working-with-lines-in-groups/11839/1 "2016-06-21T15:53:55Z")
On my HMI screens, I like certain areas to pop just a little by making them looked raised. Many items have a boarder option, Beveled - Raised, that gives the exact look I like. However the rectangle tool lacks this feature, so I made two lines using the line tool, aligned them with the top and right sides of the box and it looks great. In order to easily reuse this raised box, I grouped the rectangle and the two lines, but once I change the dimensions of the box, the lines will disappear! I get that what’s going on is that the line itself isn’t exactly getting rescaled, but the box around the line and when I squish the grouped box down, the box around the line becomes squished such that I can no longer see the line (side note, out of curiosity why is there a box around a line at all? Why not just the line by itself such as in Paint or any other program I can think of?). So what is the proper way of working with such a group that will allow me to resize a group of line without making the view area box around the line less than the width of the line itself even when resized? ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [June 21, 2016, 5:32pm UTC](https://forum.inductiveautomation.com/t/proper-way-of-working-with-lines-in-groups/11839/2 "2016-06-21T17:32:15Z")
I’m gonna guess that most people would just use a container for such areas, and set it’s border to Beveled-Raised. It has the side benefit of organizing all the components you place in it. Note that you can group items and convert the group to a container if you decide you need one after starting your design. ---
**Author:** ![JordanCClark](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jordancclark/32/83362_2.png) [@JordanCClark](https://forum.inductiveautomation.com/u/JordanCClark)\ **Post date:** [June 21, 2016, 8:17pm UTC](https://forum.inductiveautomation.com/t/proper-way-of-working-with-lines-in-groups/11839/3 "2016-06-21T20:17:45Z")
Just as a side note, groups with shapes only will not have the option of a border or converting to a container. ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [June 21, 2016, 11:35pm UTC](https://forum.inductiveautomation.com/t/proper-way-of-working-with-lines-in-groups/11839/4 "2016-06-21T23:35:33Z")
[quote=“JordanCClark”]Just as a side note, groups with shapes only will not have the option of a border or converting to a container.[/quote]Interesting. I hadn’t encountered that. I guess I would add a simple label, group, convert to container, and then delete the label. ---
**Author:** ![abishur](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/abishur/32/9096_2.png) [@abishur](https://forum.inductiveautomation.com/u/abishur)\ **Post date:** [June 22, 2016, 2:42am UTC](https://forum.inductiveautomation.com/t/proper-way-of-working-with-lines-in-groups/11839/5 "2016-06-22T02:42:05Z")
I had thought about using a container, but using a full on container seemed like it was needlessly complicating the screen when all I was doing was adding a little coloration change to denote some setpoints. If to keep things truly scalable across platforms I need to use a container I guess I can, but I’m still curious in the correct method to do what I was describing for situations where I’m seeing a similar issue but a container isn’t a viable solution.