-
-
Notifications
You must be signed in to change notification settings - Fork 233
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 Time range trigger for Multiple Trigger option. #1219
Comments
This idea isn't bad, the main issue is that currently Actions (or rather the I don't see enough value at the moment to make the architecture more complex, just for this, so I am putting this issue on hold. |
I understand, thank you for reading and responding. Would running an action with command line be considered? I might be able to achieve the same results with task scheduler. |
Command line parameters for LLT were or are something that was/is on the table, but there wasn't much push for it. I will see how much time I have, and consider making one for Actions only - maybe it's a good thing to start with. |
@BartoszCichecki I would like to give a try on this cl parameters when I finish things on my hand. Would you rather use IPC to send triggered quick actions to LLT which is already running (as a host) than just read the action list and do the job before ensuring single instance? |
I think that would work well. For right now, I've achieved this by making a few PowerShell scripts that run on login and logoff and do different things depending on the current time. |
Resolved in #1338 |
Rules
Version
2.20.2
OS
Win 11 Pro 22H2
Device
Legion S7i 16IRH8
Is your feature request related to a problem?
No
How would you like the problem to be solved?
Current LLT Supports a trigger for a specific time, The ability to have a range would be awesome.
Example: between 11 pm and 7 am && When a user becomes active; Do stuff
What alternatives have you considered?
Another approach would be the ability to run an action with the Windows task scheduler
Additional information
No response
The text was updated successfully, but these errors were encountered: