Find Results Pane Enhancement

Feature Requests Studio Features
#1

Right now the Find Results pane is quite difficult to read for large projects thanks to the fact that tabs and other whitespace are not trimmed from the start of the found lines. What a mess:

BadStuff.PNG

It would be trivial and a big improvement to at least trim the leading whitespace, and ideally the results should probably be arranged into a two-column layout (script name / line of code) rather than a simple list.

7 Likes
#2

this + a refresh search button on the window would be amazing

3 Likes
#3

For what itā€™s worth, Visual Studio is also like ROBLOX when doing a ā€˜search allā€™;

1618Ɨ543 24.4 KB

Chances are when it was first implemented they wanted it to be something like this, to which it look almost identical.

However, I do agree when a better layout is needed; I would prefer a table, looking something like this;

          File | Line | Text
-------------- | ---- | --------------------------------
      Test.lua |    1 | print("OMG HI")
GameScript.lua | 1234 | print("This is a debug message")

(Unfortunately, CommonMark does not include tables so I had to manually format that using a code block)

#4

Visual Studio (at least the later versions, not sure what is in your screenshot) also has a built-in widget that also does a ā€œfind allā€ but formats it properly, and you can click the items to jump to the code.

#5

Iā€™m using Visual Studio 2015 (with update 3) in that screenshot; and thatā€™s the only thing I know which allows you to do a find all. Mind telling me where this is? :stuck_out_tongue:

#6

Hmm never mind, it appears the one I meant only works for semantic nodes (definitions, variables etc). And you can also click the lines in the output you show anyway, so the benefit is minimal. Getting rid of the leading whitespace and/or having actual columns would be great though, not sure why itā€™s so crappy even for VS.

#7

we all forgot about the card and it died

idk why it was ā€œtoggleable leading whitespaceā€ when just trimming it is what we want and way faster to implement. new card time?

#8

Yeah, thereā€™s no need for a toggleā€¦ I canā€™t think of any reason you would want the indentation.

As far as in comments / disabled scripts, Iā€™m not sure that thatā€™s entirely desirable behavior. Especially disabled scripts: Just because the code isnā€™t currently running doesnā€™t mean that itā€™s not important to know about in a find. Dead code is a source of a lot of bugs if it gets used / reenabled later on.

#9

Yeah that was my own separate idea that I ended up not wanting to push cuz gollygregā€™s suggestion was way better lol

#10

Done. No more pesky whitespace in the find widget.

4 Likes