Ability to see the PlayerGui Topbar within studio

As a feature request, the ability to see the PlayerGui Topbar within Roblox studio would greatly benefit developers because they would be able to view the 36 Topbar Y-axis pixels which is only seen during a running session / game. As a Roblox developer, it is hard to design and visualize GUI components that are within the PlayerGui topbar area. Right now, the viewport in Roblox studio does not represent the actual screen viewport, because it does not include the PlayerGui Topbar dimensions.


Not being able to see the PlayerGui Topbar in studio editing makes it hard to design GUIs that go within that space. If the issue is addressed, it would make it easier for developers to visualize and design GUIs, and visualize the actual viewport.


Replying to EchoReaper’s post below:

(I made the key points bold for a quick read)


“If your UI is affected by a 36p offset, you’re probably not designing your UI right” ~EchoReaper

As a real world example, I am developing a game right now, and I have a compass GUI at the very top of the screen. Being an experienced UI designer, I designed the GUI to be adaptable for different aspect ratios, and it also shifted up 36 pixels to account for the topbar (meaning that my GUIs are designed correctly, it’s just that there was an unnecessary obstacle which can reoccur for other GUIs as well).

To develop this particular GUI, I had to design it at a lower UDim2 Y-value position so that the GUI wouldn’t clip out of the viewport in studio - and then once it was designed, I shifted it up 36 pixels. I consider this an issue that shouldn’t be an issue (because it doesn’t make sense that the Topbar dimensions are not visible in the Roblox Studio viewport during editing). There is no doubt that it would greatly benefit the majority of Roblox developers considering that developers have to account for the 36 pixels which isn’t even in the Roblox Studio-Edit viewport.

“If your UI properly adapts to these, then it will handle the 36p offset of the topbar fine as well.” ~EchoReaper

For you and I, correctly positioning, and resizing GUIs is easy (despite not being able to see the topbar), but a large quantity of developers do not account for the 36 pixel difference within an actual game session. For example, I’ve seen lots of developers design a GUI background frame using the following: Frame Size = {1, 0, 1, 0}, Position = {0, 0, 0, 0}… This does not account for the 36 topbar pixels, meaning that their GUI frame will not cover the entire screen as seen within the current Roblox Studio editing viewport. This common mistake can be easily prevented by displaying the topbar within studio edit mode.

I don’t see any reasons to why we should not include the player GUI topbar within the Roblox Studio editing viewport.


Replying to Captain_Goobles’ post below:

image

This is a “possible” solution, but then GUIs centered at {0.5, 0, 0.5, 0} will then be slightly offset, as well as other GUIs that adapt to screen / viewport size. This would be creating more problems than fixing problems. Thank you for your idea though.

Simply having the Roblox Studio “edit-mode” viewport 36 pixels taller (making the topbar area visible) would make it easier to design a few GUIs in that space, without having to worry about the other GUIs being affected by the 36 pixel offset using “IgnoreGuiInset”.

9 Likes

If your UI is affected by a 36p offset, you’re probably not designing your UI right. There are an endless amount of resolutions and aspect ratios users can have. See common desktop resolutions and common mobile/laptop resolutions. And that isn’t even counting if the user resizes the window. If your UI properly adapts to these, then it will handle the 36p offset of the topbar fine as well. You can use the emulator to make sure your UI works across various resolutions:

Desktop Resolutions

Standard Width Height Aspect Ratio
HD 1366 768 ~16 : 9
FHD 1920 1080 16 : 9
WXGA+ 1440 900 16 : 10
other 1536 864 16 : 9
HD+ 1600 900 16 : 9
XGA 1024 768 4 : 3
WXGA 1280 720 16 : 9
WXGA 1280 800 16 : 10
SXGA 1280 1024 5 : 4
WSXGA+ 1680 1050 16 : 10
QHD 2560 1440 16 : 9
HD 1360 768 ~16 : 9
nHD 640 360 16 : 9
WUXGA 1920 1200 16 : 10
SVGA 800 600 4 : 3
QWXGA 2048 1152 16 : 9

Laptops

Device Width Height Aspect Ratio
Dell XPS 13 1920 1080 9 : 16
Apple MacBook 12-inch 2304 1440 5 : 8
Acer Chromebook 1366 768 16 : 9
Samsung Chromebook 1366 768 16 : 9
Apple MacBook Pro 13-inch 2560 1600 5 : 8
Microsoft Surface Book 3000 2000 2 : 3
Apple MacBook Air 13-inch 1440 900 5 : 8
Apple MacBook Pro 15-inch 2880 1800 5 : 8
Apple iMac 27-inch (Retina 5K Display) 5120 2880 5 : 8
Apple MacBook Air 11-inch 1366 768 5 : 8

Phones

Device Width Height Aspect Ratio
Apple iPhone 7 Plus 1080 1920 9 : 16
Apple iPhone 6 Plus 1080 1920 9 : 16
Apple iPhone 8 Plus 1080 1920 16 : 9
Apple iPhone 6s 750 1334 9 : 16
Samsung Galaxy S8+ 2960 1440 5 : 9
Samsung Galaxy S 480 800 3 : 5
Apple iPhone 5 (5c, 5s) 640 1136 40 : 71
Samsung Galaxy S6 1440 2560 9 : 16
Samsung A5 720 1280 9 : 16
Samsung Galaxy J7 720 1280 9 : 16

Tablets

Device Width Height Aspect Ratio
Apple iPad Pro 2732 2048 3 : 4
Apple iPad Mini 768 1024 3 : 4
Apple iPad Air 2 2048 1536 3 : 4
Apple iPad Air 2048 1536 3 : 4
Apple iPad Mini 4 2048 1536 3 : 4
Apple iPad Mini 2 2048 1536 3 : 4
Microsoft Surface Pro (2017) 2736 1824 3 : 2
Huawei Mat 1920 1080 16 : 9
Samsung Galaxy Tab S2 2048 1536 4 : 3
Amazon Fire 1024 600 5 : 8
3 Likes

Some people build UI elements into the top bar, and for those who want to, it can be trivial to start with if you don’t know how large the top bar is or what your UI would look like behind it.

I think being able to emulate Roblox’s CoreGui, visually, in combination with your game’s GUI, could be valuable to see whether the player list or chat may be in the way, or to build elements into it.

However, this can be accomplished similarly by enabling this option in settings, and by taking a copy of the RobloxGui ScreenGui, which has all the CoreGui elements in it.

image

2 Likes

FYI there is a checkbox in the screengui object that takes care of the 36 pixel offset for you: “IgnoreGuiInset”

3 Likes