Not sure what happened, but as of this morning, it appears that the expressive output window is mostly broken now.
@GeneralRelish if the team is in need of any system info or logs, feel free to have an engineer message me and I can provide them with any information they may need.
Thanks for reporting! A fix for this will be available shortly after this weekâs release. Weâre still working on the column logic so please report any other weird behavior!
For everyone in the thread reporting performance concerns - we hear you! Most of our current effort is going towards performance improvements. We will get close to parity with the old output window but there will always be a small performance cost incurred for the ability to print and dynamically expand tables. We recognize that this may be an issue for some workflows (e.g. logging), so weâve included a âLog Modeâ setting that removes table printing and retains performance parity with the old output.
After the latest update the output widget displays incorrectly:
Is this some sort of bug? I just opened the widget (docked to the right) and printed something.
The Log Mode feature is cool though.
Edit:
The mouse also seems to get stuck to the scrollbar occasionally, effectively preventing any input in Studio at all - might post a bug report when I get more details about its reproduction.
Looks like a combination of things - your Context column is word-wrapping but the column is really narrow so you get the string of letters. And the headers have disconnected so you canât adjust. Bad, but we should have fixes for everything rolling out soon.
Please file a bug for the mouse-on-scollbar behavior if you can reproduce it. This sounds new and unfortunate. 
This is also happening to my friend and I.
This issue is happening to everyone on our dev team as well following todays update. The Expressive output window is now unusable and we have all been forced to disable it.
This is a known issue that will be fixed in the following release. Until then we regret that switching to the log mode is the best alternative.
You think you got it bad⌠my output window is way worse. Most of the columns are squished infinity to the right, and I canât get them out. Any help?
I know how to fix this. Are you on Log Mode? If not, go to the top right corner button (the one with three dots) and press it, then click Log Mode.
Log Mode is on now, but it looks more like the old output window now. Theres no columns at all now, itâs this:
I guessed itâs better now. Thanks for your help!You can resize each column.
âŚ
This doesnt work for dictionaries? It only shows the last entry.
Try do:
print({ClassName = "Hey", Class = "Look", Classn = "it", Value = "works", Not = "not"})
Result:
I tried to resize them, but the bars to resize columns are so far to the right, they donât respond when I try to resize them.
An update was pushed now, I hope that fixed it as itâs sooo annoying.
Edit: nope.
Really like this feature but is buggy
It was pretty RIP before also, when they removed support for private modules. So I guess double-RIP?
RIP-RIP
Why would it be a private module? Itâs open source and I used to use it all the time.
Regardless, itâs pretty done with for sure now.
Bugs and scaling issues that have been addressed aside, I canât stand it for the following reasons:
local repr = require(3148021300)
local myTable = {
hello = âworldâ;
score = 5;
isCool = true;
}
print(repr(myTable)) â {hello = âworldâ, isCool = true, score = 5
True.
But the example he had on the post was that.
But yeah, he probably released it
