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
Windows.setPosition("center") still bug? #5390
Comments
Can you post your own sample app? I have the same bug, I posted it here #4766. But ignored because it cannot be reproduced, so please post your own. |
@kkm @mscreenie I cannot reproduce this issue either. Could you post your OS, NW.js version and full reproducible app? |
I believe I have two monitors. I will post my sample soon. |
Sure. I'm using Windows 7 and the problem affects 13,14 and 17 last I checked. I'll post an app and try it on other machines just in case its my problem. |
Sample app: https://ufile.io/58c16
|
The root cause is that If you want your window always pinning to the center of the screen, hook up If you want to move it immediately to center just once, you can manually calculate and set window's |
Thank you the explanation. I didn't realize it was async. My users are still using 12.3 and this issue has only been present in above. I'm guessing after setPosition has been called I should remove the eventHandler? Thanks. |
You can use |
@kkm If your bug is the same as mine - Could you close this? Seems like the method was async. |
I want to know, is that bug or still development?
The text was updated successfully, but these errors were encountered: