21.60.0104 - Quick Search Not Working As Before With Escaped Characters

Things you’d like to miss in the future...
admin
Site Admin
Posts: 60357
Joined: 22 May 2004 16:48
Location: Win8.1 @100%, Win10 @100%
Contact:

Re: 21.60.0104 - Quick Search Not Working As Before With Escaped Characters

Post by admin »

Let me reply with a picture:
Attachments
QuickSearchFindFilesToggle.png
QuickSearchFindFilesToggle.png (7.07 KiB) Viewed 575 times

Jerry
Posts: 805
Joined: 05 May 2010 15:48
Location: The UnUnited States of America

Re: 21.60.0104 - Quick Search Not Working As Before With Escaped Characters

Post by Jerry »

admin wrote: 29 Mar 2021 11:13 Let me reply with a picture:
Oy, didn't realize that toggle persists!
Running on Windows 10 Pro 64-bit quad-core ASUS G752-VY notebook with 64 GB RAM, over 26 external USB3 drives attached via multiple powered hubs with letters and mount points, totaling 120+ TB.

jupe
Posts: 2757
Joined: 20 Oct 2017 21:14
Location: Win10 22H2 120dpi

Re: 21.60.0104 - Quick Search Not Working As Before With Escaped Characters

Post by jupe »

@Don: I assume because of this topics modifications, I have noticed a recent change in quicksearch behavior, it might not affect all OS's (because of folder layout), but now with "Follow Junctions" enabled, doing a QS in my user folder results in an "Access Denied" pane message (not dialog), just thought I would mention it as its possibly a regression. For me to repro I can just run a QS such as %USERPROFILE%?*.txt with the previously mentioned junctions setting enabled. The change in behavior is since 21.60.0100 but not sure which exact build was last working, let me know if you want me to narrow it down to a build.

admin
Site Admin
Posts: 60357
Joined: 22 May 2004 16:48
Location: Win8.1 @100%, Win10 @100%
Contact:

Re: 21.60.0104 - Quick Search Not Working As Before With Escaped Characters

Post by admin »

Oh yes, got it. :tup: Indeed a regression, caused by work on the "Files and non-empty folders" Branch View. Fix comes.

Checking for this I found something even more evil (and new): possible overflow crash. Fixed as well.

Post Reply