-
Notifications
You must be signed in to change notification settings - Fork 849
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
Hide on autostart #230
Hide on autostart #230
Conversation
Doesn't seem to work for me on windows 10. |
Also doesn't work on win7 |
Any help from the community here? @razzeee Teamwork/node-auto-launch#31 seems to reference |
That's what we're trying to use. I'm just not sure if our exe understands --hidden or if they have a bug not even setting that |
@yuya-oc Would you have any thoughts? |
Not applicable for OS X. In my thoughts, apps should handle |
Well the mac implementation isn't trying to use --hidden |
var appLauncher = new AutoLaunch({ | ||
name: 'Mattermost' | ||
name: 'Mattermost', | ||
isHidden: true |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I misunderstood the changelog. This part is called when uninstalling the application. So you should use isHidden
in settings.jsx
which enables auto-start. Then, possibly main.js
have to handle the --hidden
flag.
Changed and now it's writing the registry key correctly. But it's like you said, electron doesn't understand --hidden for windows |
Any thoughts from the community here? |
Would be nice to know if this implementation works on osx and Linux. Then we just need to figure out why windows doesn't. |
Not need to test on OS X because auto-start is not implemented. Please see #164. |
I see, thanks @yuya-oc , @timroes @jnugh Would love to have your help checking if the desktop app stays minimized after autostart when logging in to a Linux machine. If either of you would like to try, you can download an artifact here: https://circleci.com/gh/mattermost/desktop/539#artifacts |
Doesn't seem to work on my system (Arch x64, pretty custom window manager - so perhaps someone with a regular Desktop Environment should test). But looking at the generated desktop file:
and looking at the source code of So there might be some problems with the generation of this desktop file. Also I tried starting the above mattermost with Could you point me to the source parts, where |
I thought the hidden would be handled by electron packager as that's responsible for building the executeables etc. But it seems like it doesn't or is not responsible for the handling. |
Does not work for me (Unity). auto-launch generates a desktop file in |
Yeah. It should :-) But apparently for me the hidden isn't in the generated desktop file. If the electron wrapper doesn't handle the hidden flag, and you don't do it, that might some the mystery why it isn't working. |
https://github.com/Teamwork/node-auto-launch/blob/master/src/index.coffee#L14 When running this directly from your branch, without using the artifacts, things work like expected. |
99ef9c2
to
d4efee6
Compare
563bcc3
to
ef76628
Compare
Version 3.0 got rid of the ES6-Promise dependency, not sure how to fix that for us and get it building again. Changelog doesn't seem to involve a fix for our problem. |
Adding a |
@timroes @jnugh |
Minimized autostart works for me :) |
@razzeee works for me too (custom window manager, Archlinux x64), but brings me back to another problem, which I will open another ticket for (skip taskbar hints). |
db78920
to
bc154f5
Compare
Upstream just merged and release Teamwork/node-auto-launch#39 Let's wait for the artifacts |
Awesome! I tried looking for the artifacts earlier today in CircleCI but couldn't find them.. @yuya-oc are they located elsewhere? Added for v1.4 so we can speed up the testing. |
Thanks! Just tested (Windows 10, 64-bit) and it didn't auto-start for me when I restarted my machine. I have |
I have tested .zip and setup.exe on Windows 10 64-bit, and .deb on Ubuntu 14.04 64-bit. They are working well. @jasonblais Would you check again? |
Hmm okay, maybe the issue was on my end. |
Tested; works on Windows 10 after disabling and re-enabling the @yuya-oc helped troubleshoot and likely related to me running a v1.3 version where auto-start might have been disabled. The setting is not overwritten unless you disable and re-enable it in the settings UI (if you simply click 'Save' on the settings page without a change, the option will remain to what it was before in the registry). Investigating whether an easy fix for v1.4/3.4 or if we leave it for the next version. For this particular PR however, we're good to go. Thanks everyone! |
So I will change the behavior when saving options in settings. It would always update the registry info. Thanks! |
Please do that in a pr and give me some heads up, as I have some problems On Tue, Sep 13, 2016, 18:03 Yuya Ochiai [email protected] wrote:
|
This should hopefully address #228
Untested so far, will grab the artifacts from ci, as soon as they are up and test those.
Let's hope Teamwork/node-auto-launch#31 is solved.