Search Issue Tracker
Won't Fix
Won't Fix in 1.7.X
Votes
0
Found in [Package]
1.4.15
1.7.3
Issue ID
UVSB-1784
Regression
No
Can’t open Fuzzy Finder when Visual Scripting Graph is undocked
How to reproduce:
1. Open the attached file "ASB Virtual Scripting SRP.zip"
2. Open asset "newgraph" (Assets>newgraph)
3. Change the position and size of the Script Graph and Editor windows as in the photo "errorposition.png"
4. Select the Script Graph window and press the right mouse button to open Fuzzy Finder
Expected result: Fuzzy Finder is opening
Actual result: Fuzzy Finder isn't opening
Reproducible with: Bolt 1.4.15 (2019.4.28f1, 2020.3.15f2), Visual Scripting 1.7.2 (2021.1.16f1, 2021.2.0b6) 1.7.3 (2022.1.0a5)
Notes:
- If the windows are positioned like in the photo "errorposition.png" bug is happening
- If the windows are positioned like in the photo "noerrorposition.png" bug isn't happening
- If the bug is happening console is showing the error "errorpositions.png"
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Foldout arrow indent is misaligned in the Inspector when used in Custom Type
- [Android] The Player screen turns black when playing a video under certain conditions
- Search window icons at the bottom are cut off when Search window is resized vertically
- "Try something else?" text label is cut off when searching for a long text in the Search window
- Rendering Debugger window sections do not have a minimum width set when resizing with the slider in the middle of the window
Resolution Note:
This will not be fixed
Resolution Note (1.7.X):
We were not able to reproduce on Linux, which is the OS the user reported he was having problems on, we were not able to reproduce on Windows either, and on macOS the user was able to reproduce consistently, however, this was due the fact that there is a property on the preferences "Limit Fuzzy Finder Height" that comes checked by default, as soon as we asked for this to be unchecked the user did not experience this issue anymore.