-
Notifications
You must be signed in to change notification settings - Fork 33
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
[Bug] Automation scripts are loaded twice at startup #15
Comments
This is probably the same as TypesettingTools#168 . In particular, it only comes up in the portable build by default, and can be circumvented by changing the autoload path under Preferences > Automation. We discussed possible solutions back then, the simplest one just being deduplication of the autoload paths. But I didn't implement this yet, mostly because this seemed like more of a workaround than a fix. But I'll see if I can implement this now or find a better solution. |
It turns out that the above commit didn't properly fix this, so reopening for now. Will fix soon. |
Fixes #168 Fixes arch1t3cht#15
Fixes #168 Fixes arch1t3cht#15
Steps to reproduce
What should happen?
It should take roughly the same time to start either version of Aegisub.
What has happened?
arch1t3cht/Aegisub takes twice as much time to start as Aegisub DC.
Software version
Tested on Aegisub 2317062 and 3aeca6d Windows portable installation.
Windows 11 Home 21H2.
My guesses
I noticed that every automation script is listed twice in arch1t3cht/Aegisub's automation menu (I don't mean scripts written in MoonScript; Those are listed four times). I assume this is the cause to the slow startup.
Thank you!
The text was updated successfully, but these errors were encountered: