You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the problem or limitation you are having in your project
Built-in scripts (i.e. scripts embedded inside a scene), as much as I like them, they have one rather significant issue - when you try to search for something in all scripts, sometimes it's difficult to know which script the result belongs to.
Example:
I searched for something and got results in different scenes. However when I click the result, instead of opening the script and pointing me to the particular line, only the scene is opened. Many of my scenes have multiple embedded scripts, so finding the relevant script can be a hassle. #4567 would help a bit, but it could be handled better.
Describe the feature / enhancement and how it helps to overcome the problem or limitation
When using "Find in Files" and there are results in built-in scripts, clicking the result should open that script, instead of only the scene.
Describe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams
One solution I have in mind is to keep track of script's line range within a scene. I.e. for each built-in script, while the scene is being loaded, the script could remember the starting line and ending line inside the TSCN file. When clicking a built-in script search result, the scene line would be translated to a specific script contained within that range.
This information would be stored only in editor builds.
If this enhancement will not be used often, can it be worked around with a few lines of script?
The best workaround right now is to use external editor for searching, but it's inconvenient if you use the built-in script editor normally.
Is there a reason why this should be core and not an add-on in the asset library?
It's about editor usability.
The text was updated successfully, but these errors were encountered:
Describe the project you are working on
Big project with many built-in scripts.
Describe the problem or limitation you are having in your project
Built-in scripts (i.e. scripts embedded inside a scene), as much as I like them, they have one rather significant issue - when you try to search for something in all scripts, sometimes it's difficult to know which script the result belongs to.
Example:
I searched for something and got results in different scenes. However when I click the result, instead of opening the script and pointing me to the particular line, only the scene is opened. Many of my scenes have multiple embedded scripts, so finding the relevant script can be a hassle. #4567 would help a bit, but it could be handled better.
Describe the feature / enhancement and how it helps to overcome the problem or limitation
When using "Find in Files" and there are results in built-in scripts, clicking the result should open that script, instead of only the scene.
Describe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams
One solution I have in mind is to keep track of script's line range within a scene. I.e. for each built-in script, while the scene is being loaded, the script could remember the starting line and ending line inside the TSCN file. When clicking a built-in script search result, the scene line would be translated to a specific script contained within that range.
This information would be stored only in editor builds.
If this enhancement will not be used often, can it be worked around with a few lines of script?
The best workaround right now is to use external editor for searching, but it's inconvenient if you use the built-in script editor normally.
Is there a reason why this should be core and not an add-on in the asset library?
It's about editor usability.
The text was updated successfully, but these errors were encountered: