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
This concerns an editor feature that is used in any project with many files.
Describe the problem or limitation you are having in your project
Whenever I search for a file from the FileSystem tab, or from the Quick Open Script or Quick Open Scene, I cannot use spaces to delimit specific tokens I want to include in my search. Instead it treats my entire entry as a single, exact string sequence to search against. This is very inconvenient especially in a large project where I might know parts of what a filename contains, but not the order, or what is between them.
For example, if I search for wizard skill, it returns no results if my file is named: wizard-skill.gd, wizard_skill.gd, skill_wizard.gd, or wizard_combat_skill.gd, etc. The expected behaviour is for all for these filenames to be returned if they exist.
Describe the feature / enhancement and how it helps to overcome the problem or limitation
With this proposed change to the search box algorithm, the expected behaviour described above is achieved.
Describe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams
We can refer to the existing search boxes for nodes (like the one in the Scene tab), or the project search functionality in Unity which is very similar to our own but does not have this issue.
If this enhancement will not be used often, can it be worked around with a few lines of script?
No, it is core editor functionality.
Is there a reason why this should be core and not an add-on in the asset library?
The suggested change is intended to be an improvement of a core feature for all users, not an opt-in feature for specific use cases.
The text was updated successfully, but these errors were encountered:
Calinou
changed the title
Make search boxes for files treat spaces the same way as search boxes for nodes.
Make search boxes for files treat spaces the same way as search boxes for nodes
Feb 21, 2024
Describe the project you are working on
This concerns an editor feature that is used in any project with many files.
Describe the problem or limitation you are having in your project
Whenever I search for a file from the
FileSystem
tab, or from theQuick Open Script
orQuick Open Scene
, I cannot use spaces to delimit specific tokens I want to include in my search. Instead it treats my entire entry as a single, exact string sequence to search against. This is very inconvenient especially in a large project where I might know parts of what a filename contains, but not the order, or what is between them.For example, if I search for
wizard skill
, it returns no results if my file is named:wizard-skill.gd
,wizard_skill.gd
,skill_wizard.gd
, orwizard_combat_skill.gd
, etc. The expected behaviour is for all for these filenames to be returned if they exist.Describe the feature / enhancement and how it helps to overcome the problem or limitation
With this proposed change to the search box algorithm, the expected behaviour described above is achieved.
Describe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams
We can refer to the existing search boxes for nodes (like the one in the
Scene
tab), or the project search functionality in Unity which is very similar to our own but does not have this issue.If this enhancement will not be used often, can it be worked around with a few lines of script?
No, it is core editor functionality.
Is there a reason why this should be core and not an add-on in the asset library?
The suggested change is intended to be an improvement of a core feature for all users, not an opt-in feature for specific use cases.
The text was updated successfully, but these errors were encountered: