Originally created by @pschopen on GitHub (Mar 2, 2021).
I just experienced an expectable bug: When having "allow discharge" enabled, an external monitor won't work when the Macbook is closed. Probably because the Macbook thinks not to be charged which generally prevents an external monitor to work if the Macbook is closed.
No idea, if that's easy to fix or one needs to live with it. Just wanted to mention the issue.
Originally created by @pschopen on GitHub (Mar 2, 2021).
I just experienced an expectable bug: When having "allow discharge" enabled, an external monitor won't work when the Macbook is closed. Probably because the Macbook thinks not to be charged which generally prevents an external monitor to work if the Macbook is closed.
No idea, if that's easy to fix or one needs to live with it. Just wanted to mention the issue.
Hi @aktivde,
as @vividfog already pointed out, this is a known problem and we are not sure if we can do anything about it.
We will definitely include a warning in the app in a future update.
@MatthiasKerbl commented on GitHub (Mar 2, 2021):
Hi @aktivde,
as @vividfog already pointed out, this is a known problem and we are not sure if we can do anything about it.
We will definitely include a warning in the app in a future update.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @pschopen on GitHub (Mar 2, 2021).
I just experienced an expectable bug: When having "allow discharge" enabled, an external monitor won't work when the Macbook is closed. Probably because the Macbook thinks not to be charged which generally prevents an external monitor to work if the Macbook is closed.
No idea, if that's easy to fix or one needs to live with it. Just wanted to mention the issue.
@vividfog commented on GitHub (Mar 2, 2021):
#114
Known issue. The download page mentions this, but the app itself doesn't. I also filed this once.
@MatthiasKerbl commented on GitHub (Mar 2, 2021):
Hi @aktivde,
as @vividfog already pointed out, this is a known problem and we are not sure if we can do anything about it.
We will definitely include a warning in the app in a future update.