# Container and sizing questions in perspective **URL:** \ **Category:** Ignition\ **Tags:** perspective\ **Created:** [October 28, 2026, 1:39am UTC](https://forum.inductiveautomation.com/t/container-and-sizing-questions-in-perspective/117631 "2026-10-28T01:39:34Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![tornel](https://avatars.discourse-cdn.com/v4/letter/t/c57346/32.png) [@tornel](https://forum.inductiveautomation.com/u/tornel)\ **Post date:** [October 28, 2026, 1:39am UTC](https://forum.inductiveautomation.com/t/container-and-sizing-questions-in-perspective/117631/1 "2026-10-28T01:39:34Z")
Hello, I have been put in charge of reproducing screens created in another software using Ignition Perspective. We are currently using Ignition 8.3.8 with Perspective module 3.3.8. Part of the process has already been completed, but they have some issues when viewing on screens of varying resolutions. The resolutions I am aware of are 1280x1024, 1680x1050, and 1920.1080. I will post some screenshots below to help better explain where I am having trouble. As far as I can tell, the original screens are using a Coordinate Container to hold everything. I am somewhat confused on what properties need to be where. In the below screenshot, currently the item named Breddo has a width of 1920 and a height of 930. Should these be set to the most common screen size possible? Or if everything is configured properly, should these be set to something else? Then there is the root item. It has mode set to percent which from what I read is what we want for resizing purposes. Then there is the coordinate container. Am I looking at it right that a coordinate container is placed inside of the root coordinate container? Is there a reason to not just put everything in the root container? The coordinate container is also set to percent mode. I have also tried various values here for apsectRatio such as viewWidth:{view.props.defaultSize.width} + ':' + {view.props.defaultSize.height}. In the other screenshots below, you can see some examples of things that do not line up properly once they are displayed on screens of different resolutions. The valves and the motor are coordinate containers under a separate folder from the screens (Views/Object vs Views/Screens). Other objects of similar design appear to scale fine, and I haven't been able to see any large difference in them and why they work. They all have their mode set to percent. I think I have the text scaling figured out, I just need to dial it in. Any tips are appreciated though. On a related question, these process screens are in the P&ID style. Is the coordinate container the best for this? I am willing to start over completely if it makes sense and is the best practice in the long run. I.e. if using a Flex container or another type would be better. I know this is a long post, and I greatly appreciate any advice. ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/2/c/2c09356de1281a1787110ddef715ab8121e8fd1c.png) ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/4/a/4aa305bd14054198bbaf1248341bf0b65b23fb71.png) ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/8/d/8dcffd40a0d63e04e337351173ff648679fd71ed.png) ---
**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\ **Post date:** [October 28, 2026, 11:54pm UTC](https://forum.inductiveautomation.com/t/container-and-sizing-questions-in-perspective/117631/2 "2026-10-28T23:54:56Z")
> [@tornel](#): > > Should these be set to the most common screen size possible? Or if everything is configured properly, should these be set to something else? In "ideal" Perspective configuration, coordinate containers should be largely avoided; they are mostly to be used for P&ID style screens or other situations where you need to position multiple components relative to each other. 80% of the time for Perspective you want (nested) flex containers, which let you care a whole lot less about exact pixel screen sizes. In general, if you _are_ using coordinate containers, you should design with them almost the same as you would in Vision - set to the _smallest_ practical size (with the correct aspect ratio, if applicable) you can to lay out your components correctly, and _optionally_ allow the user agent to scale them **up**. Trying to design things to lay out at **exact** dimensions against a certain monitor never works, because inevitably browser chrome/OS framing/whatever changes and so things won't be exactly the resolution you want. > [@tornel](#): > > Am I looking at it right that a coordinate container is placed inside of the root coordinate container? Is there a reason to not just put everything in the root container? You are correct. Generally nesting a coordinate container inside a coordinate container has no _layout_ benefits, but has some benefits/tradeoffs in terms of locating sibling components for bindings (if you're using the intermediate container to "encapsulate" custom properties and not deeply nesting bindings up and down). > [@tornel](#): > > I have also tried various values Aspect ratio **should not** be dynamic. You should set it to an explicit ratio that matches the content you have and then not touch it.