PHPStorm 10 randomly ignores AltGr +8/9 to open brackets - phpstorm

I have a weird situation with the new version of PHPStorm 10.0.2.
I have a german keyboard and to open square brackets [] i need to type a combination of AltGr + 8 or 9 keys.
All works ok until, at some point in time, randomly, this combinations are ignored and they are being interpreted as Alt+Strg (Alt+Ctrl on englisch keyboard) + 8 or 9 which jumps from curly brackets up and down.
This issue happens in Windows. Will update this question when I get to a linux machine, in case i can reproduce it.
german keyboard layout is the default one on the machine so no other languages.
Anyone has this issue and how can this be solved?
UPDATE 1:
If i press Alt + AltGr and 8 or 9 it works correctly...
UPDATE 2:
I tried in Linux ctrl+alt does not have the same effect like on windows. So it is a windows only issue

This was driving me insane!!!
However, it was not random (though I initially thought it was).
Steps to reproduce (German keyboard):
Open IDE
Open first project (AltGr + 8 or 9 will work as expected)
Open second project in a new window (AltGr + 8 or 9 will now start to switch projects and no longer work until only one window remains)
Steps to fix:
Open <SYSTEM DRIVE>\Users\<USER ACCOUNT NAME>\.<PRODUCT><VERSION>\config\options\keyboard.xml (e.g. C:\Users\John\.WebIde100\config\options\keyboard.xml)
Set "USE_NON_ENGLISH_KEYBOARD" to false

Did you enable "German layout support" option? See IDEA-142462 - may be related. Enabling actionSystem.force.alt.gr=true (https://youtrack.jetbrains.com/issue/IDEA-91975#comment=27-384169) may help...

Related

Unable to hide “Chrome is being controlled by automated software” infobar within Chrome v76

This is not really a new question, nor an answer to the original question, but is rather a request for clarrity since the answer posted to the original question is incomplete, but any request for clarrity gets deleted...
Original post is here... Unable to hide "Chrome is being controlled by automated software" infobar within Chrome v76
So, while I understand your original answer, we do not use managed instances of Chrome, and we all run on Windows 10 Home Edition... so, this setting your answer is not an option for us. On the other hand, all of our regression tests are failing now because this stupid banner is in the way of everything.
Is there a way a non-IT-Managed user running Windows 10 Home Edition can suppress this banner?
If not, how does Google expect us to continue using Chrome for testing? Any suggestions greatly appreciated... Also, I am using Python, so if you supply code example, please keep that in mind... this is what I am currently doing, and it was working before last week, but not working now...
options = webdriver.ChromeOptions()
options.add_argument('--start-maximized')
options.add_argument("--disable-infobars")
options.add_argument("--disable-extensions")
options.add_argument("--disable-automation")
options.add_argument("--log-level=3")
# options.add_argument('headless')
options.add_argument('window-size=1920x1012')
options.add_experimental_option("prefs", {"download.prompt_for_download": False})
options.add_experimental_option("prefs", {"plugins.plugins_list": [{"enabled": False, "name": "Chrome PDF Viewer"}]})
options.add_experimental_option("prefs", {"download.default_directory": os.path.abspath(context.BaseResultsDir + '/Downloads/')})
options.add_experimental_option("prefs", {"download.extensions_to_open": "applications/pdf"})
context.driver = webdriver.Chrome(chrome_options=options)
After much Googling, this is finally what worked for me... Updated Selenium, switched to Canary release of ChromeDriver, and then made these adjustments to my test code, which is Python...
# options.add_argument("--disable-infobars") <<< TOOK THIS OUT
# options.add_argument("--disable-automation") <<< TOOK THIS OUT
options.add_experimental_option("excludeSwitches", ["enable-automation"]) <<< PUT THIS IN (Finding this one was the real killer)
options.add_experimental_option("useAutomationExtension", False) <<< PUT THIS IN
Your solution and mine are very similar. Thank you for posting.
David
Probably reason behind settings for infobar was working still last week not in this week, are may be you have updated/autoupdated chromedriver or chromebrowser. However your setting to disable infobar are not working because as per this commit on - Jan 10 2018, --disable-infobars option has been removed from chrome options
Solutions - Keeping this line does nothing options.add_argument("--disable-infobars") you can remove it.
options.add_argument("--disable-automation")
This line makes real confusion here towards the solution because there are 2 different ways to do it (By default this switch is enabled we have to remove it to disable the infobar). This line disables the password saving UI for more details read this nice discussion
Use this line do disable the infobar by excluding enable automation switch -
options.add_experimental_option("excludeSwitches" , ["enable-automation"])
It solves the problem to some extent, when I tried with this intermittently developer code plugin popup comes up and ask to enable/disable it. and it wont go away by options.add_argument("--disable-extensions") this. If you facing same issue use another switch to disable it as below-
options.add_experimental_option("excludeSwitches" , ["enable-automation","load-extension"])
This solves the problem from root(load-extension switch supports Chromedriver v2.33 and later). However there is one more way to disable the developer code plugin popup which you can do by adding --disable-plugins into shortcut of chrome
If these solutions doesn't work for you then chromium command line switches here can help you to customize the chrome behavior
Additionaly ChromeDriver(Capabilities capabilities) is deprecated and can be used as
capabilities = DesiredCapabilities.CHROME.copy()
capabilities.update(options.to_capabilities())
driver = webdriver.Chrome(chromedriver, desired_capabilities=capabilities)
solution to disable infobar in Java
options.setExperimentalOption("excludeSwitches", Arrays.asList("enable-automation" , "load-extension"));
will disable infobar with developer code plugin
This worked for me:
options.add_option('excludeSwitches', ['enable-automation'])
Method add_experimental_option, I suppose, is removed from the latest versions.

PhpStorm navigate to -> file search only for Twig files

I have strange problem connecting with PhpStorm IDE. I use version 2016.3.2 Build #PS-163.10504.2.
I love using Ctrl + Shift + N for searching files which I need to override. I have 2 project (one new, one old) and in old file searching works fine and in new search only for twig files and nothing else.
Is there any configuration I need to change?
Check filter -- the blue Funnel icon on the right top corner of that popup -- you may have selected to list files of certain types only.
Otherwise -- try universal File | Invalidate Caches... and restart IDE -- it usually helps in such "suddenly stop working" situations.

Sikuli Key.CTRL does not work

Using Sikuli IDE 1.0.1 (according to the "About SikuliX" menu).
Ubuntu 14.04.3, 64 bit, virtual server, via tightvnc + Xfce 4.
One day everything just stopped working though we did not change the sources. Server updates (ubuntu software) are off. Combinations like type('a', Key.CTRL) started to type plain 'a' char, not selecting a text (as before).
We even tried to spin up the same instance type, set everything up there, and run agian. And Sikuli failed to type "Ctrl" again!
We also tried to run the script with "-r", skipping IDE. Same thing - no Ctrl.
Can anybody help?
Thanks!
I suppose you should do it as sequential actions (like you actually do on your keyboard):
keyDown(Key.CTRL)
type("a")
keyUp(Key.CTRL)
Alternatively, you can use the KeyModifier.CTRL in the function type
type("a", KeyModifier.CTRL)
If you're using the
type('a', Key.CTRL)
to simulate holding CTRL and pressing the 'a' key, the method you're using has been depricated. It should more properly be
type('a', KeyModifier.CTRL)
as per the documentation.
Try that and see if that will solve your problem. :)

WebStorm/PhpStorm, issue with terminal on Windows 10

I decided to try Windows 10, but having problem to make terminal works inside WebStorm/PhpStorm.
When I open terminal, sometimes it's completely black, sometimes it loads the project folder but I cannot type there. There is a way to run it in the external window, but I just got accustomed to work with console like internal window inside WebStorm/PhpStorm...
I tried cmd, Power Shell - same results.
Any ideas?
Workaround: Terminal works fine in Windows 10 if you use legacy console.
To do so, open a command prompt window, right click on the title, then select Properties. At the bottom, check "Use legacy console". Confirm the dialog window and go back to WebStorm to launch a new terminal. It should work.
In any case, this is the ticket to watch after:
https://youtrack.jetbrains.com/issue/IDEA-143300 -- star/vote/comment to get notified on progress.
UPDATE:
This issue has now been resolved -- the fix will arrive in next major version -- PhpStorm v10/WebStorm v11 (or whatever that version will be as long as it's based on 142.xx branch or newer).
UPDATE:
For those who have problems with right clicking and finding "Properties" menu entry:
Just for the record: I have confirmation from JetBrains that it will be fixed (i.e. work with non-legacy mode) in WebStorm 11 which is scheduled for the beginning of November. In the EAP version it should already work.

Can't comment code in phpStorm using cmd+/ if selected code is right after php opening tag

I am having an annoying problem and I don't know if this is the default behavior or if I did something wrong (maybe accidentally changed some configuration values?).
When I am trying to comment code using keys cmd+/ and cursor is (or selection begins) on the code line right after opening php tag, nothing happens (see screenshot below)
but if I move cursor (or start of selection) by one line, commenting code with cmd+/ works fine (see screenshot below).
Am I missing something, could anyone confirm this behavior or maybe someone knows a solution to this annoying problem?
I am using phpStorm 7.1 (Build #PS-133.982) on Mac OS 10.9.2
By the way Cmd+Alt+/ works fine on both cases, but it creates block comment, not line comment.
Well, I can confirm this behaviour on 7.1.3 on Windows 7 x64 SP1.
But it works just fine in v8 EAP build 136.1255
You can try EAP build yourself (you can run it alongside with v7 -- just not the same project in both IDEs at the same time) -- http://eap.jetbrains.com/phpstorm