Skip to content
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

[Feature Request] Command Line Argument to (Gracefully) Close Flow Launcher #3113

Closed
EnigmaSolved opened this issue Dec 7, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@EnigmaSolved
Copy link

This is in relation to conversation in #2684 about running Flow in portable mode on Microsoft OneDrive (or similar) in order to use the same installation and settings across multiple machines (in lieu of a true Settings Sync like the above item is requesting).

I would like to be able to script (probably via Windows Task Scheduler) to gracefully shutdown Flow whenever I lock my computer, and then re-launch Flow whenever I unlock. The reason being that if I change my settings on one computer I want those to be loaded by Flow on other computers, and since it appears that Flow saves settings files on exit it seems prudent to me to try to automate things like I'm describing.

However, I cannot seem to find a command line argument that will gracefully Close/Exit Flow. I know I could forcibly Kill Flow, but that is less desirable -- I'd really prefer Flow be able to do any normal shutdown processes

I have tried arguments like close, CloseApp, kill, exit, shutdown, but all that happens is the Flow window launches -- none of these get Flow to actually Close/Exit.

Thanks for considering my request and/or for any assistance in determining the correct Command Line Parameter!
:)

@EnigmaSolved EnigmaSolved added the enhancement New feature or request label Dec 7, 2024
@EnigmaSolved
Copy link
Author

On further experimentation, it may actually be better to just kill the process. The settings files appear to get written to immediately when a setting is changed, and then get written to again on Flow shutdown. For my purposes it may actually be better to avoid the later, so I will close this request for now (but may reopen it in the future, depending on how further testing goes).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant