PHPStorm 2017.2 basic editing issues
Hi all. I'm not sure if it is my machine, the combination of software that I have running etc. but I am finding the basic editing functionality with 17.2 awful. For example, I select a block, press delete, if I start to type, nothing appears, just the previous entered character at the point where I deleted the previous block. Also, I have multiple projects open. I cannot switch between them using the keyboard short-cut nor does selecting the project in the drop down window menu do anything. I have to physically click on the window. This is on a Mac running the latest and greatest.
Anyone else experiencing these issues? Thanks in advance.
Jon
Please sign in to leave a comment.
Sorry - just checked the storm log and it is full of the following:
2017-07-24 10:11:28,240 [263157387] ERROR - enapi.editor.impl.DocumentImpl - Editor is already disposed
com.intellij.openapi.util.TraceableDisposable$DisposalException: Editor is already disposed
at com.intellij.openapi.util.TraceableDisposable.throwDisposalError(TraceableDisposable.java:94)
Anyone any the wiser?
Hi there,
To start with -- please try disabling all custom (not bundled by default) plugins -- maybe you have one that is interfering/not fully compatible.
Other than that (I'm not a JB personnel and not a Mac user) -- use "Submit a Request" link on the top of the page -- it's more suitable for the case like you are currently seeing.
Thanks for coming back to me Andriy - will do
Hi
Whilst I havent had your problems (and Im on Linux not mac) I have noticed some issues since the 2017.2 release
I use the Ctrl-Shift-n shortcut to gain access to the "find file to open" option and several times you can see the popup open and close back down again immediately and so if i'm not keeping a close eye on the screen I end up typing in part of the filename into the code editor instead.
Sometimes have to press it 2 or 3 times to get it to come up and stick on screen. Am considering seeing how easy it is to revert back to 2017.1 just to prove to myself that it is the 2017.2 but I guess the easiest answer for me is to install it in a virtual machine as 2017.1, confirm everything is okay and then upgrade to 2017.2 to confirm its broken and then report the bug. As Andriy said, if you dont have any third party plugins and you still have the issue, then its worth reporting.
@Tony Byng
Your case is rather Linux specific: https://youtrack.jetbrains.com/issue/IDEA-173000
There are few possible workarounds mentioned there -- try them.
Andriy - Many thanks.