This update is quite an update
Undo and Redo are actions that can be put in a custom tab if you didnāt try that.
It looks like it already has something to undo on a new place, it does something to VideoService?
Age old known issue. Basically harmless, the only result is output spam.
This is a great and thoughtful write-up. I will make sure weāre tracking these. Thanks for taking the time do it!
Yeah, actually the problem is the background is too light. Color updates coming soon!
Light mode in particular has a bunch of known issues we will be fixing up with color updates. I hope to be able to bring back the custom icons directory but right now we are actively changing icon sizes (in pursuit of reducing wasted space) and our icon pipeline + engine are pretty particular.
We will just make the auto-hide work better and snappier. The stop button is a known issue we are tracking.
The tab truncation is a good point and Iāll get a ticket in for us to look into that.
What are you up to @TenebrisNoctua
Why is it expected for us to do that though. They are pretty fundamental and extremely useful when it comes to changing anything (and have existed in studio since forever) so itās such a weird change to remove them from their designated area and have the user manually place them back on a ribbon where we now have an extra button to click to reach them. It would make way more sense to just place them next to the playtest buttons like they were previously rather than have us unintuitively go about adding them to a new tab to readd something everyone uses
Iāve been using this new beta for a few days now and these are my thoughts so far. Iāll continue updating this as I encounter more things.
Some behavior/features Iād like to see restored from the Qt UI:
- In the Qt UI, when selecting a script to view, you automatically go to the scripting tab. In this new UI, that no longer happens, and I have to manually open the scripting tab, which adds friction in my workflow.
- There used to be the Step In, Step Over, and Step Out buttons in the scripting tab. Theyāre now super tiny buttons in the top left when debugging, which isnāt great.
- The controller emulator is completely gone.
- Reload script option is completely gone (add drafts back to scripting tab)
Bugs:
- When a panel is open, itās usually indicated by having the button made a lighter color. This doesnāt work for some buttons at all, such as for the Breakpoints, Call Stack, and Watch buttons under the Script tab.
- The Drafts widget (which contains the reload script option) cannot be added to custom tabs.
- The Reset Pivot option is grayed out and unselectable until you first edit the pivot on a
PVInstance
, after which point, the option remains selectable. (Iād like to see this option always selectable when a PVInstance is selected without needing to enable Edit Pivot)
Since people might have a preferred scripting tab as they can make custom tabs, they no longer take you to the built-in one. You should be able to add buttons to custom tabs as well, so if you need large debugging buttons, you can do that now.
Hopefully reloading scripts can be added to custom tabs in the future though as that is good for testing. I didnāt realize it was missing until you pointed it out.
I would recommend using the keybinds for this to save time. Some other services donāt even use buttons for these actions anymore such as notion.
The buttons were nice to have regardless since they provided a visual cue (being shaded out) on if you were able to undo/redo in the first place. I used both the shortcuts and the buttons in tandem for this reason. Also everything can technically be a shortcut but that doesnāt excuse removing buttons people have been using since the beginning of the platform for seemingly no reason
If something can be made into a shortcut, I am ALL for removing buttons for the same action. But that isnāt for everyone. Maybe they can compromise by allowing people to pin buttons beside the playtest controls? They could separate it with a divider.
I donāt think thats a good philosophy to have. A lot of times doing shortcuts can be awkward (doing Ctrl+Y or Ctrl+Shift+Z just feels terrible to me) or miss out on certain context (like I said the undo/redo buttons being able to signal if there were steps available). Redundancy is perfectly fine in certain contexts such as this and removing the buttons doesnāt really have a solid justification. Although yeah being able to edit the pinned buttons would be nice although since its on the same line as the tab buttons it could potentially interfere. Not a big fan of the UI redesign as a whole just feels super out of touch and more like its trying to cater to a potential mobile/console audience rather remaining functional for PC users
A more important question:
When are we going to see this color as the main background for the Studio?
It looks very cool.
Since they are removing buttons, I donāt see that to be the case. Especially because studio isnāt compatible with either as far as Iām aware. Also, mobile prioritizes large buttons ā not removing them entirely.
And again, not everyone is the same. I use my operating system almost entirely with keybinds (opening apps (win+1 opens my chrome, etc), closing apps, shutting down, basically any action), and only use my mouse to navigate inside of apps. The same is true when I code as itās always faster to press a keyboard shortcut than a button. Everyoneās workflow is different, and so this will need to accommodate as many people as necessary.
And yes having small pinned icons on the tablist could get in the way, but a simple zindex change would solve that issue. Tabs would need to take priority over pinned shortcuts, but because the icons are small anyways it wouldnāt be a huge issue.
Thatās what I mean though. The undo/redo buttons are large now, at the cost of having to add them to a tab which removes them from being universally accessible. The rest of the design choices made like the new tab system as a whole and extra padding around buttons points to them wanting to move studio to places like mobile in the future, at least in my eyes. I think being fluent in key binds is important and a lot of people such as yourself choose to go that route when interacting with their computer, but like I said you still lose out on things like those visual cues. Itās just a weird and unnecessary change in my eyes considering nobody complained about them and they have been a staple of studio since the beginning
Flip it around the other way: Why would you expect space in the ribbon to be spent on Undo / Redo?
The hotkeys for them are basically universally understood and usually the faster way of accessing that functionality.
Even if you donāt have your hands on the keyboard to use the hotkey, Undo / Redo are available without a hotkey through the system menu (Edit ā Undo). I do sometimes want to invoke undo without reaching for the keyboard but not enough that an extra click to get it from the system menu is annoying.