-
I noticed that with https://github.com/seerge/g-helper/releases/tag/v0.189, 421dc0c implemented a battery limit that should be applied a bit earlier compared to having to wait for the user logon. The question might be stupid, but after checking the code and the correct creation of the task I notice that GHelper.exe is run with the TL;DR Instead of just task scheduling on system startup Lines 56 to 61 in 0a89062 This is mainly a question, not really a feature request. The apparent feature request is just to prove an example of a plausible usage. As always, thank you for pouring your time and effort into this project. Your dedication is greatly appreciated! |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
@Constrat if you run "main" GHelper.exe process on system startup it just won't show icon in system tray and windows refuses to create main app window. So UI becomes completely inaccessible. (you can verify it by yourself) It's either "service-style" process on startup, or a regular UI-app on logon. I don't want to create real service, clone different processes, etc - so G-Helper just schedues it's own exe with a special param to do only thing that is worth running before login - charge limit :) |
Beta Was this translation helpful? Give feedback.
@Constrat if you run "main" GHelper.exe process on system startup it just won't show icon in system tray and windows refuses to create main app window. So UI becomes completely inaccessible. (you can verify it by yourself)
It's either "service-style" process on startup, or a regular UI-app on logon.
I don't want to create real service, clone different processes, etc - so G-Helper just schedues it's own exe with a special param to do only thing that is worth running before login - charge limit :)