-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Position new windows on the same screen as N1, even if that isn't the primary screen #58
Comments
Hey @jaredly thanks for downloading N1. This is definitely something I've been feeling as well. It looks like we're specifying a width and height for new windows, but not positioning them. (Though the feedback one we actually are trying to position above the button—that's interesting...) Will check it out! |
@Sunno that top-right issue should be fixed as of today's update |
The same situations as @jaredly has. |
Does this issue still occur? |
I can not reproduce. "new message" window appears left aligned on the horizontal center of the screen. |
@alex-bender Do you have multiple monitors? If so, when you say left aligned on the horizontal center, do you mean between the multiple screens? |
Yes, I have multiple monitors. And yes, it is between the screens. But I just realized that couple weeks ago I have swap prime and secondary monitors. So for now "new message" window appears on primary screen, doesn't matter where is the main window of Nyla's situated. Tomorrow I will install latest version and try again. |
@alex-bender What OS are you again? |
Firstly OS: |
@alex-bender Hey, the window will open in its last state because of
|
I haven't ~/.nylas/main-window-state.json file. |
Another request: #2999 |
Another request: #3002 |
I have N1 open on my secondary screen, but when I click "new message" or "manage account" or the "feedback" button, they all appear on my primary screen.
This is rather annoying.
Thanks for an awesome product! I'm excited to use it once the sync has finished ;)
The text was updated successfully, but these errors were encountered: