I broke it.
json
{
"_comment": "I wonder what would happen if you added json files under the CustomRibbonTabs folder near where plugins are installed.",
"Name": "stuff",
"Controls": [
{
"Id": "Select",
"Type": "IconButton",
"Action": {
"PluginId": "BuilderTools",
"DataModel": "Standalone",
"ItemId": "Select",
"Category": "Actions"
}
},
{
"Id": "Move",
"Type": "IconButton",
"Action": {
"PluginId": "BuilderTools",
"DataModel": "Standalone",
"ItemId": "Move",
"Category": "Actions"
}
},
{
"Id": "Scale",
"Type": "IconButton",
"Action": {
"PluginId": "BuilderTools",
"DataModel": "Standalone",
"ItemId": "Scale",
"Category": "Actions"
}
},
{
"Id": "Rotate",
"Type": "IconButton",
"Action": {
"PluginId": "BuilderTools",
"DataModel": "Standalone",
"ItemId": "Rotate",
"Category": "Actions"
}
},
{
"Size": "Large",
"Type": "Separator"
},
{
"Type": "Row",
"Children": [
{
"Type": "Column",
"Children": [
{
"Id": "MoveGridSize",
"Type": "Spinbox",
"Setting": {
"PluginId": "BuilderTools",
"DataModel": "Standalone",
"ItemId": "MoveGridSize",
"Category": "Settings"
}
},
{
"Id": "RotateGridSize",
"Type": "Spinbox",
"Setting": {
"PluginId": "BuilderTools",
"DataModel": "Standalone",
"ItemId": "RotateGridSize",
"Category": "Settings"
}
}
],
"Tags": "X-ColumnSpace100"
}
],
"Tags": "X-RowSpace200"
},
{
"Size": "Large",
"Type": "Separator"
},
{
"Type": "SplitButton",
"Id": "Part",
"ShowSettingOptions": true,
"Setting": {
"PluginId": "BuilderTools",
"DataModel": "Standalone",
"ItemId": "PartShape",
"Category": "Settings"
},
"DefaultAction": {
"PluginId": "BuilderTools",
"DataModel": "Standalone",
"ItemId": "Insert/Block",
"Category": "Actions"
}
},
{
"Id": "Anchor",
"Type": "SplitButton",
"DefaultAction": {
"PluginId": "BuilderTools",
"DataModel": "Standalone",
"ItemId": "Anchor",
"Category": "Actions"
},
"Setting": {
"PluginId": "BuilderTools",
"DataModel": "Standalone",
"ItemId": "AnchorMode",
"Category": "Settings"
},
"Children": [
{
"Children": [
{
"Id": "AnchorMode",
"Type": "RibbonToggle",
"ActionOnToggle": {
"PluginId": "BuilderTools",
"DataModel": "Standalone",
"ItemId": "AnchorTool",
"Category": "Actions"
},
"Setting": {
"PluginId": "BuilderTools",
"DataModel": "Standalone",
"ItemId": "AnchorMode",
"Category": "Settings"
}
}
],
"Type": "Row"
}
],
"FastFlag": "LuaRibbonAnchorLockModes"
},
{
"Id": "Anchor",
"Type": "SplitButton",
"Action": {
"PluginId": "BuilderTools",
"DataModel": "Standalone",
"ItemId": "Anchor",
"Category": "Actions"
},
"Children": [
{
"Children": [
{
"Id": "AnchorMode",
"Type": "RibbonToggle",
"Action": {
"PluginId": "BuilderTools",
"DataModel": "Standalone",
"ItemId": "AnchorMode",
"Category": "Actions"
}
}
],
"Type": "Row"
}
],
"FastFlag": "!LuaRibbonAnchorLockModes"
}
]
}
was working until I updated studio
1 Like
just please give us the option to keep the old UI, cuz I personally hate the new one. This “next gen” studio UI is more like the “new gen” UI, or maybe it’s just the next discovery in the field of dogsh—, idk, but please don’t force this update thanks.
2 Likes
Any future (awesome) updates they have for us next year & beyond… won’t work on the current (soon old) UI. That’s what they have been telling us.
Just like Windows XP & Vista … there is no more support - the same is happening with Studio.
Yeah… we don’t like change … but I am sure it will be much for the better.
I myself will wait for the proper release - current works for me - future looks better.
2 Likes
Very cool Roblox Studio team, very cool
1 Like
Completely different framework, completely different language, no point in keeping the old UI.
8 Likes
On a previous thread I got told you guys would deal with the excess space this UI takes compared to the old one but it seems you havent done that
When will that get done???
Okay, I wasn’t too sure about the next gen studio update, but now It isn’t so bad.
i tried to make a screenshot button but what are the actions for it or the doesnt exist?
2 Likes
Its Large
Hello, Good update!
Does that mean the old QT UI will be completely replaced? And does that impact performance and stability?
For the most part, however sone Qt will drive things like the Menu Bar
Probably not, if it would it would be positively from state being tracked a lot better with the new system
1 Like
i still dont understand how to make buttons, can someone reply with a example json with
- studio-related buttons
- plugin buttons
- seperators
if you know more
4. dropdown buttons
1 Like
This is awesome! I can’t wait to use this!!!
This looks amazing! I find myself jumping through tabs a lot, this should reduce this quite a bit. One question: will plugins be able to create their own ribbon tabs? I’m picturing what plugins with lots of controls like Moon Animator could do with an entire tab.
1 Like
While this sounds nice, it’s unreasonable to expect the team to backport all their features to an old UI that uses an entirely different framework from the new one. I agree that the next-gen UI can use a little work, especially when it comes to space usage, but I have faith that it will get better over time, as it is still in beta.
heres a suggestion:
you should make it so that you can toggle the new material picker or the old legacy style material picker
These buttons need to be fixed. If I click on one of the red dots, the button does not activate. If a user clicks on one of those red spots they are 100% intending on pressing the button. The size of the hitbox needs to include the text + padding
5 Likes
they can keep the same UI design but rebrand it with a better backend.
The new UI style looks way better than whatever qtitanribbon stuff studio uses idk why some of you like it so much
4 Likes