-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Disappearing Slic3r Window after disconnecting from second monitor. #1116
Comments
@FidelCapo Would you please try to reproduce it? |
Hello,
I can do this over and over all day long. I just have to remember, before I close Slic3r that I have to move it to my laptop screen. Then I can unplug the external monitor and still get to slic3r.
However, If I have Slic3r open and pull the external monitor then it relocates to my laptop monitor just fine.
Thanks,
…-Bao
On Aug 2, 2018, at 11:32 AM, bubnikv ***@***.***> wrote:
@FidelCapo <https://github.com/FidelCapo> Would you please try to reproduce it?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#1116 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AC8Rg00ViHvjXa19M-DNXz35sG0Cs2iXks5uMzehgaJpZM4VsqIh>.
|
We were able to reproduce it on both OSX and Windows. We hope to fix it for the final release. |
Thank you!
You guys really are amazing!!!
…-Bao
Sent from my iPhone
On Aug 3, 2018, at 6:37 AM, bubnikv ***@***.***> wrote:
We were able to reproduce it on both OSX and Windows. We hope to fix it for the final release.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Version
Slic3r Prusa Edition - 1.40.1+ (Mac)
Operating system type + version
Mac OS 10.13.6 (High Sierra)
Behavior
Slic3r window does not re-locate to main display after disconnecting from secondary monitor.
Is this a new feature request? No.
This is probably related to Issue #129 and #925.
The text was updated successfully, but these errors were encountered: