-
-
Notifications
You must be signed in to change notification settings - Fork 325
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
Add support for Everything v1.5a #1716
Comments
Just to confirm, you have tried manually setting the path to 1.5a (via app's settings at the bottom)? |
Facing the same issue. And no, setting the path doesn't work. |
Disable the 1.5a Instance To use the Everything 1.4 SDK you will need to disable the "1.5a" instance. Have you tried this? |
Thank you @taooceros. Changing alpha_instance from 1 to 0 in the .ini file made it possible for 1.5a to work with the launcher. |
Thank you, this was super simple and helpful! |
This issue is stale because it has been open 45 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
Thanks for this. In my case, I also had to set this in the user settings file under the hidden AppData folder. |
you can set alpha_instance to false in the advanced options tab of Evergthing's UI |
Hello, I'm using Everthing 1.5a . It seems that this plugin can't detect it and gives a "Warning: Everything service is not running". Clicking on it doesn't seem to solve the issue and I get no feedback from doing that.
Initially I assumed that the problem was the service name, but following @void's instructions to disable the alpha version's instance naming didn't solve the issue. Unfortunately I didn't have time to check if that indeed changed the name back to 1.4's.
Although this is a niche problem, I wonder if it makes sense to provision for cases like that on the plugin's side, for futureproofing as well.
At any rate, thank you for your sharing your code.
The text was updated successfully, but these errors were encountered: