No response when running atom at one side of desktop (Windows) #9901
Comments
Same issue for me, Atom 1.2.4, Windows 10 desktop. |
I can't seem to make this happen, following the same steps. Win 10 added an extra step after Win+Right where it wants you to pick a windows for the other side of the screen - did you pick something there? I tried pressing esc there as well as picking a window and not seeing this. |
The extra step in Win 10 can be disabled in System / Multitasking / 'When I snap a window, show what I can snap next it'. I turned that on and off, I haven't seen any significant difference on issue, I leave it off.
|
I haven't been able to reproduce this either. Like @raelyard I originally hit that extra step where it wants me to select a window so then I disabled the extra step in System/Multtaking like @psallandre mentioned and tried the alternative steps. Still no dice. 😖 I'll try to take another stab at it later. |
I can't reproduce this on Windows 10 using 1.4.0-dev-f2155fa, and I've always had the extra snap feature disabled. |
I've the same problem on Win10: Win + RIGHT -> no draw until window resize Really annoying bug. Disabling extra snap is not an option. |
I'm having this exact same issue. Also on windows 10. |
I'm having exact same issues. @50Wliu did you enable the Windows 10 snap feature when you tested? |
Odd, I just managed to reproduce this when testing what @LondonAppDev suggested.
Atom 1.5.0-dev-c34ef24. I can't tell whether this is due to me running Electron 0.36 or not though. In addition I can't seem to reproduce it reliably. |
I have not reproduced with any of the steps described here - simply snapping to right or left as half-screen does not exhibit the behavior for me. I did, though, find steps to reliably reproduce (on my machine - seems pretty inconsistent experiences). Extra snap enabled/disabled makes no difference - it happens either way. Also happens reliably in Slack, so must be Electron.
|
@raelyard try doing it with two instances of Atom. Load the first instance, snap left, then load the second instance and snap right. 100% of the time my right one freezes until I unsnap it. I am opening a new instance by right clicking a directory and clicking "Open with Atom" |
@LondonAppDev not getting the same result. Two instances doesn't seem to matter and I have yet to see the problem with following your steps. |
Adding my voice - I can definitely confirm this issue, and it happens when I drag or use WIN+arrow, and I only ever have one instance/window open at a time. |
I get this issue all the time (Currently atom@1.5.0-beta3, Windows 10). I think it only happens when the window remains the same size before and after the snapping. Easiest way to get a window of the same size is to snap a window and then use |
This will likely be fixed in #9627 |
@benogle Nice! |
@maxbrunsfeld Will this change land in |
I am getting this problem in 1.6.0 |
I'm running 1.6.1 and it seems to be working fine now. I'll comment, should I run into the problem again. Everything works now as far as I can tell! |
I will upgrade and retest at home to see if there are scenarios (it works fine for me with win7 at work, just win 10). Your earlier comment about it only happening when the window is the same size - thats not the case for me. |
No this still happens. As @MajorBreakfast pointed out above it only occurs when the window is not resized. I'll raise a new bug. |
This is confirmed fixed in 1.7.0 (& present in 1.6.0,1.6.1, 1.6.2) |
This issue has been automatically locked since there has not been any recent activity after it was closed. If you can still reproduce this issue in Safe Mode then please open a new issue and fill out the entire issue template to ensure that we have enough information to address your issue. Thanks! |
I have a problem with atom (version 1.2.4) on my Windows 10 laptop. In Windows we can split the view and run applications side by side using Win+LEFT or Win+RIGHT key. When we run atom at one side, even if we keep atom at front, typing keyboard won't have any response until the window is restored or maximized.
Here is the way to reproduce the problem.
The text was updated successfully, but these errors were encountered: