-
-
Notifications
You must be signed in to change notification settings - Fork 261
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
(Custom scripts issue) [SystemUnlock] Event changes the theme but does not trigger scripts execution #811
Comments
Hey, thanks for the detailed report!
At startup, ADM has no way of knowing which state the system is in when it comes to user scripts as it can't track what the user is doing when the application is not active. The reason you're not seeing the SystemUnlock event triggering your script is actually not because the trigger defective, but because there is a
event that predates the trigger events you are looking to use. Since you're on Windows 10 and you have See: 776a22f I've pushed a new beta build that fixes a DWM refresh issue with the theme mode that you encountered, as well as disallowing time synchronization theme switches to occur during the lock screen, which should yield the correct event. Lemme know if that fixes your issue. What you're experiencing is sort of a cumulative result of multiple little bugs with the theme mode, gotta squash them one by one. |
Indeed, after disabling that, it now works correctly.
|
Description
[SystemUnlock]
event changes the theme, but does not start script execution.As I see it, other triggers check the time anyway, somehow using
[TimeSwitchModule]
.But then why does the script execution not work?
P.S. I also noticed that
[TimeSwitchModule]
is also triggered at system startup, and the current theme is recognized asUnknown
:log
Expected Behavior
No response
Log Data
service.log
scripts.yaml
config.yaml
Full
service.log
Commit Hash, Version and Windows Build
7b6b6eb
10.4.2.2
3.1.4
1.3.3.0
8.0.0
19045.3803
Screenshots / Videos
Image
The text was updated successfully, but these errors were encountered: