you know it’s good when missmandypanda posts it
1 Like
This actually seems useful and good for those ui experts out there.
I’ll still try to use it tho
We’re getting there.
I would love to know the ETA on detached attachments (detachments?) for when it’ll be pushed to the client. It’s probably the last Studio beta that I utilize.
8 Likes
I don’t know what I did or how to reproduce this error, but here’s the output and a screenshot of the hierarchy. Trying to open the style editor again does nothing. I’m using the Next Gen Topbar beta.
StyleEditor.StyleEditor.Packages._Index.Scheduler.Scheduler.forks.SchedulerHostConfig.default:315: StyleEditor.StyleEditor.Packages._Index.Scheduler.Scheduler.forks.SchedulerHostConfig.default:292:
------ Error caught by React ------
GetDerives is not a valid member of StyleRule "ReplicatedStorage.PlayerStuff.GuiManager.Design.Rough Edge.StyleSheet.Frame"
------ Error caught by React ------
StyleEditor.StyleEditor.Src.Components.TokenTable:329 function getDerivedStateFromProps
StyleEditor.StyleEditor.Packages._Index.ReactReconciler.ReactReconciler.ReactFiberClassComponent.new:223 function applyDerivedStateFromProps
StyleEditor.StyleEditor.Packages._Index.ReactReconciler.ReactReconciler.ReactFiberClassComponent.new:1019 function mountClassInstance
StyleEditor.StyleEditor.Packages._Index.ReactReconciler.ReactReconciler.ReactFiberBeginWork.new:1051 function updateClassComponent
StyleEditor.StyleEditor.Packages._Index.ReactReconciler.ReactReconciler.ReactFiberBeginWork.new:3519 function beginWork
StyleEditor.StyleEditor.Packages._Index.ReactReconciler.ReactReconciler.ReactFiberWorkLoop.new:251
StyleEditor.StyleEditor.Packages._Index.ReactReconciler.ReactReconciler.ReactFiberWorkLoop.new:1973
StyleEditor.StyleEditor.Packages._Index.ReactReconciler.ReactReconciler.ReactFiberWorkLoop.new:1858
StyleEditor.StyleEditor.Packages._Index.ReactReconciler.ReactReconciler.ReactFiberWorkLoop.new:1807
StyleEditor.StyleEditor.Packages._Index.ReactReconciler.ReactReconciler.ReactFiberWorkLoop.new:940
StyleEditor.StyleEditor.Packages._Index.ReactReconciler.ReactReconciler.ReactFiberWorkLoop.new:856
StyleEditor.StyleEditor.Packages._Index.Scheduler.Scheduler.Scheduler:306
StyleEditor.StyleEditor.Packages._Index.Scheduler.Scheduler.Scheduler:262
StyleEditor.StyleEditor.Packages._Index.Scheduler.Scheduler.forks.SchedulerHostConfig.default:240 function doWork
StyleEditor.StyleEditor.Packages._Index.Scheduler.Scheduler.forks.SchedulerHostConfig.default:276 function performWorkUntilDeadline
- Edit
Stack Begin - Studio
Script 'StyleEditor.StyleEditor.Packages._Index.Scheduler.Scheduler.forks.SchedulerHostConfig.default', Line 315 - Studio
Stack End - Studio
@font-face, you know, that thing that makes you use custom fonts
this update lowkey looks good
people saying that devs can now make complex UI is making me happy
The same could be said about images, audio, etc… and yet developers can still upload their own, this isn’t an excuse for them to not introduce custom fonts.
5 Likes
!! ISSUE HERE !!
I dont know why, but everytime I put 2 strokes with both different ApplyStrokeMode, the last setting set only show up both on the Preview, and in real time :
The border mode isn’t showing, only the contextual mode, because it has higher priority.
All I want to say is, only one of both UiStrokes show simultaneously.
1 Like
Sure, but a proper licensing process needs to be introduced first, font licensing is complex and often doesn’t allow derivative works which is an issue on a platform with UGC
1 Like
sorry for being offtopic but PLEASE add uishadow, for text or whatever frame. i don’t wanna keep going on some photo editor app and add some shadow to just one singular text. 
I’m pretty sure it’s intentional for only 1 stroke to be rendered per UI object, although a beta feature is coming soon™ to allow multiple strokes along with some new properties.
2 Likes
There should be more options for each corner in UICorners: TopLeft, TopRight, BottomLeft and BottomRight so you can customize your UIs even more natively in studio!
8 Likes
They should at least automate having every font on https://fonts.google.com/ available in the creator store
5 Likes
This is the coolest. The only thing that would make it better would be compiling down from html and css for UI
1 Like
I can finally make new & improved UI’S now! Thanks for this small but useful Roblox Studio update Roblox!
What? You have always been able to have two UIStrokes per object, this is a UIStyling specific issue.
Ah, I see. You can have 1 Border and 1 Contextual stroke per object, but not multiple. I was not aware of that.
How I would change the color of the UIStroke under my TextButton depending on the tag?
I have two tags for buttons, one named “Action” (green) and the other named “Alert” (red)
I would like the stroke color to be different for both buttons
I’ve already tried putting a “Color” index in my tag, but that doesn’t seem to work..
If there is other ways to achieve this, please let me know as I’m still learning how everything works.
1 Like
Just figured out you can’t 
You have to make the UIStroke separate, which is rather unfortunate.
Why recreate the entire Explorer and Properties window?
You just remade it in a different style, and for no real benefit.
Why not just add the ability to right-click properties in the already-existent property window, then select a variable to connect the property to. This would’ve really simplified the development of this feature, and honestly it would’ve made it even more convenient.
There’s no reason to over-complicate things. Think about it.