-
-
Notifications
You must be signed in to change notification settings - Fork 425
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
1.3.0 bug when query includes space #445
Comments
same issue, the space could not be entered. |
Not confirmed here. Windows 11 Home x64 Version 22H2 (OS Build 22621.2428) |
It's probably related to how the settings are configured. I'll have a look later. |
Same issue here. When I try to input a space, it triggers Quicklook instead. |
Same here. If QuickLook is running, I get the quicklook preview. |
It's a deskband issue (Windows 10). I'll try to get it fixed tomorrow or the day after. Sorry about that. |
I also have this issue. |
I assume you are using the deskband with ExplorerPatcher or StartAllBack? I already worked on the fix but it requires a little more effort than expected. I'm sure I will be able to release the fix by the end of this week. Sorry for the inconveniences. |
Yes I'm using StartAllBack. |
No StartAllbBack or ExplorerPatcher was used in my Win 10 machine. |
I’m using Win10 with ExplorerPatcher here, if it helps. |
The fix was released in 1.3.1. Please let me know if there are any more problems related to this. |
Preflight Checklist
EverythingToolbar Version
1.3.0.0
Everything Version
V1.4.1.1024 (x64)
Windows Version
Windows 10 Version 22H2
Steps to reproduce
Expected Behavior
I rollback to EverythingToolbar 1.2.0.0 and it can query sth like "xxx .pptx"
Actual Behavior
While using EverythingToolbar 1.3.0.0, it feels like "space" is forbidden to input
Screenshots
I will add screenshots after work.
Log output
Sorry, I heavily depend on EvertythingToolbar, so I just rollback at once.
I will try the latest release after work and add the log file.
Additional Information
No response
The text was updated successfully, but these errors were encountered: