# Is Screen\[0\] always the primary desktop when calling system.gui.getScreens() **URL:** \ **Category:** Ignition\ **Tags:** vision, scripting, ignition80\ **Created:** [December 4, 2020, 6:34pm UTC](https://forum.inductiveautomation.com/t/is-screen-0-always-the-primary-desktop-when-calling-system-gui-getscreens/41220 "2020-12-04T18:34:28Z")\ **Posts on this page:** 1\ **Showing post:** 2
**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:** [December 4, 2020, 7:01pm UTC](https://forum.inductiveautomation.com/t/is-screen-0-always-the-primary-desktop-when-calling-system-gui-getscreens/41220/2 "2020-12-04T19:01:13Z")
> [@MicroVAX\_II](#): > > Is screens[0] always the primary desktop? Unfortunately, no. Discussion here: > [@Inconsistent Screen Indexes](http://forum.inductiveautomation.com/t/inconsistent-screen-indexes/28578): > > On Ignition 7.9.11, I’m finding the screen indexes reported by system.gui.getScreens() are inconsistent across multiple workstations. These Windows 10 workstations each have 5 monitors. The OS Display Settings for each workstation all identify the displays in the same pattern: [5] [4] [3] [2] [1] However, when calling system.gui.getScreens() in Ignition, I’m getting varied results… Workstation 1: [1] [4] [3] [2] [0] Workstation 2: [0] [4] [3] [2] [1] To be clear, indexing start at… --- _[View the full topic](https://forum.inductiveautomation.com/t/is-screen-0-always-the-primary-desktop-when-calling-system-gui-getscreens/41220)._