Cool. Next up, making the command bar capable of running multi lined code instead of one lined even if it works the same way.
1 Like
you can already do that
(30chars)
2 Likes
This is So Amazing, we needed this 
1 Like
I really love this and it is VERY useful but I do have some feedback on how it looks with dark mode. (idk about light mode as my eyes can’t go through that torture again lol) Specifically the borders of the output. Why are they white?? The rest of the studios tabs have a dark grey border for a sleek look but not the new output. Is there any reason for this? And could it possibly be changed?
Normal borders (Dark grey)
New output borders (White 
)
Also thanks again for another killer studio update! Much love and appreciation to the roblox team behind this!
6 Likes
You can turn this on with the 'Show memory address for expanded tables" setting. It’s under the three dot menu in the top right. 
2 Likes
Many thanks to everyone who’s taken time to leave feedback on this thread! We’ve made a list and we’re going through it to plan fixes / upgrades. (Never fear, vertical layout peeps - we’ve heard you!)
24 Likes
Then I shall rephrase.
Allowing me to type
for i,v in pairs() do
--code
end
instead of
for i,v in pairs() do --code end
The same thing, yes, but the first example is just less confusing.
5 Likes
Yay! Now I don’t have to do table.foreach(tbl, print) when printing tables!
Excited when this comes out! Can’t wait to use it! (The UI needs a little bit of improvement)
1 Like
Two things I would like to see changed / added would be the abillity to remove columns, as I only want to see Timestamp and Message to keep the console cleaner looking, and to be able to expand tables that are printed as part of a message. E.g. print(“first module:”, tableResult).
Nice update otherwise.
1 Like
The new expressive output is pretty cool, but it is unable to print userdata. This makes debugging some of my custom objects more tedious because I cannot see if its a userdata or not. It simply displays “void”, not even showing that it’s a userdata. I really hope this isn’t intentional.
4 Likes
I really like this new update! Especially the print tables feature! Keep making this great updates!
1 Like
After enabling the beta feature, the first thing that stood out to me was all the weird white outlines around the various UI elements. It doesn’t mesh well at all with the interface and looks bad when viewed side-by-side with the other windows. Example below:
Please either remove the outlines or make them darker.
Thanks for the new features guys!
2 Likes
It’s losing the column layout changes I made, every time I reopen my project.
Original:
Changed:
But if I close and reopen Studio, the original layout is back…
10 Likes
its not every single programmer
5 Likes
Thank you. For this pretty useful update.
2 Likes
https://gyazo.com/0f05ffe9de9ad8a78f68480f88cf5d87
This is honestly making me wayy uncomfortable than i should be…
4 Likes
oh awesome. this is so much better. can’t wait for this to come out of beta 
2 Likes
This has been great to use so far! My only complaint is having to set it up again each time I open a new Studio window.
2 Likes
So, I like the idea for the output window becoming more useful. Some general comments.
- It currently seems really slow compared to the simple output. I was having trouble even scrolling through it. It also caused WaitForChild items to timeout. I had to disable this feature to keep working.
- The timestamp should include milliseconds as well.
- Because the debugger has not supported breakpoints on both the client and server for such a long time I have a logging class that all other classes inherit so the source column is not that useful for me. If I was using just print directly i can see the usefulness of it.
- I like where it is going, instead if messing with the existing print maybe make it a different function like ePrint() so you can control when you want to use it.
- Maybe consider a differ method builtin for tables like table:print(). Careful not to mess with our __tostring meta data though.
3 Likes
Not showing the keys correctly.
In my case, I have this table:
cell[1][2].Name="Inicializador"
cell[1][2].OrientationY=0
But when I print(cell) I get:
Not showing the indexes [1] and [2].
1 Like