Multi-line Command Bar, issues feedback

Feature Requests Studio Features
1

Description

Videos are attached in the private message.

A private message is associated with this bug report

 

Status:

  • The new interface no longer floats above the Command Line text box
  • I can toggle whether I want ENTER to directly trigger execution or not.
  • The ability to turn the Command Line into multi-line or single line (all in one)
    • multi-line takes extra height for a scrollbar, even though I don’t want that
    • multi-line enables highlighting that for one-line usage is horrible, especially if you paste long text
    • multi-line is laggy
  • Better ways to erase favorited content.

other issue: Multi-line Command Bar new lines do lag spikes

2

Hello! We’ve recently rolled out some improvements that address some of your suggestions for the command bar. In particular:

  • There is now a setting available to execute commands by just hitting enter, accessible in Studio Settings under Studio > Command Bar > Execute Command with Return. You can insert new lines with Shift + Enter.
  • When there is a single line, hitting up/down will navigate through your recently executed commands. When there are multiple lines, hitting up/down when at the start/end of the script will navigate as well. Ctrl+Up/Down continues to work as before.

We hope these changes help you integrate the new command bar in your workflow. We are continuing the explore additional improvements.

1 Like
3

I never created the bug report for this.

But have you ever dragged the Command Bar window out?

And then moved the cursor and dragged down? It moves to a new line, even though I didn’t create the new line. This isn’t what I am expecting out of a “one line” mode only.

This isn’t normal.

image
image820×265 3.96 KB

This is why I explicitly wrote, to switch to one-line mode. Not multi-line compressed faked into one-line, because of these bugs…

 

What happened to the font? I can’t read it. :sob:

image

The padding from the bottom, is still there.

There’s a slight bug.

  • Type in print(1)
  • Press Enter
  • Type in print(2)
  • Press Enter
  • Move arrow key up

it doesn’t immediately move to print(1), compared to the old behavior. While the old behavior had some other strange cache thing.

If you printed 3,4,5 and then 1 again. The last one wouldn’t be 1.

4

Thanks for the feedback!

And then moved the cursor and dragged down? It moves to a new line, even though I didn’t create the new line.

This is a bug. We’ve created an internal ticket for it and will look into the issue.

What happened to the font?

There is a command bar font setting available in the settings menu under Studio > Command Bar > Font.

The padding from the bottom, is still there.

Are you referring to the padding beneath the command bar’s viewport? This is actually Studio’s status bar that is used to display messages, e.g., when auto-recovery files are created.

it doesn’t immediately move to print(1) , compared to the old behavior. While the old behavior had some other strange cache thing.

This also looks like a bug. Thanks for sharing it!

1 Like
5

Oh, I know about that one.

It’s just that there’s more padding now than before. I use to believe that it may be because the new command bar saves space for a horizontal scrollbar.

Interesting, I’ll check it out once the other fixes have been made. But, why does that setting not inherit from the other font?

6

I can’t edit the original post anymore. So.

  • multi-line takes extra height for a scrollbar, even though I don’t want that

I think that’s still present.

This is less the case now, I think. Except if you create new lines, but there’s a limit if you create a lot of new lines at some point it will stop.

This is fixed by having arrow keys move up and down over CTRL + UP and DOWN when you’re not in multi-line mode. However, there seems to be a slight bug where, if you are in multi-line mode, the arrow key will cycle through the history as well without CTRL.

There’s still no

for _,v in FAVORITES do
 -- erase favorites
end

The other bugs that I remembered, were fixed :partying_face: