Today, March 19th, is the 78th day of the year.
nothing on the type color and highlight differences?
Optimizes Instance:FindFirstChildWhichIsA() 20x for parent instances with many children. Optimizes Object:IsA() 30%.
heh nice
New Explorer - Explorer no longer smooth scrolls.
Just a personal preference- I kinda liked this. Could there be a setting to toggle it?
I can finally sleep in peace if this means we can prevent parts from sleeping without hacky methods that don’t work at times.
Version 666 is indeed fast approaching…
yo??
pls tell me this will allow us to grayscale textures in-engine and apply our own tint onto it instead. i cant even use editableimages to automate this because of how limited they are rn
Speaking of scrolling.
We can’t all be so lucky…
Probably, there’s some nuance in how we actually want to approach this in the future but we know it’s desirable
what is QT?
Not much, what’s a Qt with you?
Qt is a framework for developing cross-platform applications. It’s what the bulk of Studio is written with, and it’s… not fantastic.
I won’t speak for Current Roblox here but I know in the past, they’ve had to put a lot of work into overcoming limitations with Qt and tried to actively avoid using it for things which is why Studio’s UI originally started to get rewritten as built-in plugins.
I’m actually pretty sad to see the UI being remade with react-lua, it just feels sluggish and like something is wrong with it. Compared to Qt, where it feels snappy and native
by azura here we go again
Hey, I said plugins, not React! I have my own complaints about React as a concept, but really it’s disconnected from the Qt thing.
That said, I don’t really agree with that claim. I’m old enough to remember stuff like the old pre-Lua(u) toolbox and it was not amazing in terms of performance or behavior. There were growing pains when they first rewrote it, but it’s much better than the old one ever was now.
On the flipside, I also remember when the new Output widget got released and it was borderline unusable despite being a ‘native’ Qt widget. It took a long time for it to get to where it is now, just like the toolbox.
What widgets in particular have you noticed being sluggish, if you don’t mind me asking?
We do want to make additional public APIs for scrolling control by the way, but that will take a bit more time because we want to make sure we’re exposing it in the right way.
Could be this related to the new SmoothScroll
property in ScrollingFrame?
78 is my favorite number lol
The number of the universe!
My fellow Christian developers aren’t going to like this…